Skip site navigation (1) Skip section navigation (2)

Re: Speed dblink using alternate libpq tuple storage

From: "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de>
To: "Marko Kreen" <markokr(at)gmail(dot)com>, "Kyotaro HORIGUCHI" <horiguchi(dot)kyotaro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: <pgsql-hackers(at)postgresql(dot)org>, <greg(at)2ndQuadrant(dot)com>
Subject: Re: Speed dblink using alternate libpq tuple storage
Date: 2012-01-21 11:52:34
Message-ID: C4DAC901169B624F933534A26ED7DF310861B301@JENMAIL01.ad.intershop.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> >
> > c. Refine error handling of dblink.c. I think it preserves the
> >    previous behavior for column number mismatch and type
> >    conversion exception.

Hello,

I don't know if this cover following issue.
I just mention it for the case you didn't notice it and would like to
handle this rather cosmetic issue as well.

http://archives.postgresql.org/pgsql-bugs/2011-08/msg00113.php

best regards,

Marc Mamin


In response to

Responses

pgsql-hackers by date

Next:From: Guillermo M. NarvajaDate: 2012-01-21 12:44:38
Subject: pg_dump custom format specification
Previous:From: Ants AasmaDate: 2012-01-21 10:51:55
Subject: Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group