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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-15 21:45:44 | Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |
Previous Message | Tom Lane | 2008-01-15 21:37:57 | Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-15 21:45:44 | Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |
Previous Message | Tom Lane | 2008-01-15 21:37:57 | Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |