Re: BUG #3790: pg_restore error canceling statement due touser request

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Mike C(dot)" <smith(dot)not(dot)western(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3790: pg_restore error canceling statement due touser request
Date: 2007-12-04 15:32:09
Message-ID: 28441.1196782329@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> I guess we should capture this error with a PG_TRY and silently abort instead.
> Just a NOTICE or INFO should be sufficient. Other errors should of course be
> rethrown.

This falls in the category of "destabilizing the code for purely
cosmetic reasons", and would be a foolish change to make at RC1 time.

We could change the text of the ERROR message reasonably easily,
but changing the basic transaction abort method is right out.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Gregory Stark 2007-12-04 16:54:35 Re: BUG #3790: pg_restore error canceling statement due touser request
Previous Message Magnus Hagander 2007-12-04 13:05:49 Re: BUG #3750: Invalid frontend message type 112