Re: Speed dblink using alternate libpq tuple storage

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)oss(dot)ntt(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: markokr(at)gmail(dot)com, greg(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, mmoncure(at)gmail(dot)com, shigeru(dot)hanada(at)gmail(dot)com
Subject: Re: Speed dblink using alternate libpq tuple storage
Date: 2012-03-27 02:20:42
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

I'm sorry to have coded a silly bug.

The previous patch has a bug in realloc size calculation.
And separation of the 'connname patch' was incomplete in regtest.
It is fixed in this patch.


Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
dblink_use_rowproc_20120327.patch text/x-patch 13.1 KB
dblink_connname_20120327.patch text/x-patch 1.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message limaozeng 2012-03-27 02:58:39 Can param evaluation use same estate as executor?
Previous Message Greg Stark 2012-03-27 02:17:36 Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)