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

Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY
Date: 2008-01-15 21:41:42
Message-ID: 13720.1200433302@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Hmm, aren't ParameterStatus messages sent just before Ready For Query?

No, they're sent immediately (see ReportGUCOption).  I had some ideas
in the back of my head about postponing such sends until just before
Ready For Query, with the idea of avoiding work for repeated changes
to the same variable; but it's not done yet.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-01-15 21:45:44
Subject: Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY
Previous:From: Tom LaneDate: 2008-01-15 21:37:57
Subject: Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY

pgsql-committers by date

Next:From: Tom LaneDate: 2008-01-15 21:45:44
Subject: Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY
Previous:From: Tom LaneDate: 2008-01-15 21:37:57
Subject: Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY

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