Re: [HACKERS] Continue transactions after errors in psql - Mailing list pgsql-patches

From Tom Lane
Subject Re: [HACKERS] Continue transactions after errors in psql
Date
Msg-id 2246.1114528791@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Continue transactions after errors in psql  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [HACKERS] Continue transactions after errors in psql
List pgsql-patches
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> I would far rather see people code explicit markers around statements
>> whose failure can be ignored.  That is, a script that needs this
>> behavior ought to look like
>>
>> BEGIN;
>> \begin_ignore_error
>> DROP TABLE foo;
>> \end_ignore_error
>> CREATE ...
>> ...
>> COMMIT;

> That's a lot of work.

How so?  It's a minuscule extension to the psql patch already coded:
just provide backslash commands to invoke the bits of code already
written.

> In this particular case I would actually like to
> see us provide "DROP IF EXISTS ..." or some such.

That's substantially more work, with substantially less scope of
applicability: it would only solve the issue for DROP.

            regards, tom lane

pgsql-patches by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] Continue transactions after errors in psql
Next
From: Heikki Linnakangas
Date:
Subject: Re: Cleaning up unreferenced table files