| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Client failure allows backed to continue |
| Date: | 2003-01-28 03:45:48 |
| Message-ID: | 200301280345.h0S3jnv02215@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-01-28 03:55:27 | Re: Release Scheduales: 7.2.4 & 7.3.2 |
| Previous Message | Tom Lane | 2003-01-28 03:43:25 | Re: Client failure allows backed to continue |