Re: Client failure allows backed to continue - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Client failure allows backed to continue
Date
Msg-id 200301280345.h0S3jnv02215@candle.pha.pa.us
Whole thread Raw
In response to Re: Client failure allows backed to continue  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Client failure allows backed to continue  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Why is COMMERROR not doing the longjump like ERROR?
> 
> Because it's defined to be like LOG.
> 
> A more useful reply might be that I'm not sure it's safe to abort in the
> client I/O routines.

Well, if we get an I/O error, I can't imagine why we would continue
doing anything --- are any of those recoverable?  Do we need a separate
error type for I/O messages?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Client failure allows backed to continue
Next
From: Tom Lane
Date:
Subject: Re: Release Scheduales: 7.2.4 & 7.3.2