Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Re: Speed dblink using alternate libpq tuple storage
This is fixed version of dblink.c for row processor. > i'll re-send the properly fixed patch for dblink.c later. - malloc error in initStoreInfo throws ERRCODE_OUT_OF_MEMORY. (new error) - storeHandler() now returns FALSE on malloc failure. Garbage cleanup is done in dblink_fetch() or dblink_record_internal(). The behavior that this dblink displays this error as 'unkown error/could not execute query' on the user session is as it did before. regards, -- Kyotaro Horiguchi NTT Open Source Software Center
Attachment: dblink_use_rowproc_20120131.patch
Description: text/x-patch (11.8 KB)
Description: text/x-patch (11.8 KB)
In response to
- Re: Speed dblink using alternate libpq tuple storage at 2012-01-30 11:42:20 from horiguchi.kyotaro
Responses
- Re: Speed dblink using alternate libpq tuple storage at 2012-01-31 07:19:22 from Marko Kreen
pgsql-hackers by date
Next: From: Josh Berkus Date: 2012-01-31 03:07:52 Subject: Re: [GENERAL] Why extract( ... from timestamp ) is not immutable? Previous: From: Tom Lane Date: 2012-01-31 01:41:17 Subject: Re: [GENERAL] Why extract( ... from timestamp ) is not immutable?