> I'd like to see a TODO item to allow an *option* to be set to choose > between these two transactional behaviours. > - abort on error > - continue on error i.e. COMMIT can/might succeed - though there are > still cases where it cannot, such as a serializable exception. > > That's a major change I agree, but the first step to its implementation > is to agree that it might be desirable to allow it.
At a minimum we need to stop forcing a rollback just because we have a syntax error. It makes development a complete pain in the butt and is one of the most, "WTF" looks I get when I am training. postgres=# begin; BEGIN postgres=# create table foo (bar ints); ERROR: type "ints" does not exist postgres=# create table foo (bar int); ERROR: current transaction is aborted, commands ignored until end of transaction block postgres=# Sincerely, Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match