Simon Riggs <[EMAIL PROTECTED]> writes:
> On Mon, 2008-01-14 at 18:46 +0000, Tom Lane wrote:
>> Fix an ancient oversight in libpq's handling of V3-protocol COPY OUT mode:
>> we need to be able to swallow NOTICE messages, and potentially also
>> ParameterStatus messages (although the latter would be a bit weird),
>> without exiting COPY OUT state. Fix it, and adjust the protocol
>> documentation
>> to emphasize the need for this. Per off-list report from Alexander Galler.
> My reading of this is that previously a PQgetCopyData() operation would
> fail mysteriously because of
> i) a reload of postgresql.conf, following the setting of any of the
> following parameters client_encoding, DateStyle, TimeZone, and
> standard_conforming_strings.
> ii) any previous LISTEN command on the session running the COPY
Neither of those events could trigger it, because neither would be
processed midstream during a COPY (in the current code, anyway).
As best I can tell:
* NOTICE messages are a risk, especially if you have a more-verbose-
than-normal client_min_messages setting.
* ParameterStatus could be a risk if a function executed during COPY
tried to change one of the above-mentioned parameters. Since COPY OUT
doesn't fire triggers, I think user-defined datatype output functions
would be the only possible candidates for that.
* LISTEN/NOTIFY isn't a risk because the backend only sends NOTIFY at
transaction end, period.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
