Re: [HACKERS] Re: light dawns: serious bug in FE/BE protocol handling - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Re: light dawns: serious bug in FE/BE protocol handling
Date
Msg-id 22931.924903534@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: light dawns: serious bug in FE/BE protocol handling  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <maillist@candle.pha.pa.us> writes:
> If you get elog(ERROR), can't you just abort the current message, and
> send the elog(), or is it very involved.

You can do that in the COPY case (good thing too), but not in the SELECT
case; if part of a D or B (data) message has already been flushed out to
the frontend then there's no way to stay in sync except to complete the
message.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter T Mount
Date:
Subject: Re: ERROR: index_rescan: invalid amrescan regproc ???
Next
From: pourreza
Date:
Subject: Low Performance