From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: savepoint improvements |
Date: | 2007-01-21 18:37:45 |
Message-ID: | 45B3B2F9.8050108@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-21 18:45:00 | Re: savepoint improvements |
Previous Message | Tom Lane | 2007-01-21 18:28:08 | Re: savepoint improvements |