Re: [HACKERS] Re: light dawns: serious bug in FE/BE protocol handling

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: light dawns: serious bug in FE/BE protocol handling
Date: 1999-04-23 21:38:54
Message-ID: 22931.924903534@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)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

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 1999-04-24 13:51:33 Re: [HACKERS] Low Performance
Previous Message Peter T Mount 1999-04-23 21:23:37 Re: ERROR: index_rescan: invalid amrescan regproc ???