Prev: [HACKERS] pgstatindex still throws ERROR: value "3220078592" is out of range for type integer
Next: psql: ON_ERROR_STOP command-line flag for scripts
From: Mike Toews on 7 Jun 2010 12:32
Hey hackers,

I routinely run SQL scripts using pgsql -f myscript.sql. If there is
an error mid-way in a large script file, due to the default
ON_ERROR_STOP=0, I see repeated�"ERROR: �current transaction is
aborted, commands ignored until end of�transaction block" until the
end of the script. Often the error is buried at the top of the output
and the following commands are meaningless or misleading messages with
a last ROLLBACK at the bottom. This is�particular�relevant to new
PostGIS users running postgis.sql that missed a step somewhere.

I know I can either embed a non-SQL command in the SQL file or add
--set�ON_ERROR_STOP =1 to the command arguments, however I'd like a
simpler command interface�(just like there is -q / --quiet for QUIET).
Could I suggest a new�command-line option -r / --on-error-stop for
psql? I have limited programming with C, should I bother submitting a
patch, or is someone else eager?

Thanks for your consideration.

-Mike

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] pgstatindex still throws ERROR: value "3220078592" is out of range for type integer
Next: psql: ON_ERROR_STOP command-line flag for scripts