On Mon, 2007-01-22 at 09:25 -0500, Merlin Moncure wrote: > On 1/21/07, Tom Lane <[EMAIL PROTECTED]> wrote: > > "Jaime Casanova" <[EMAIL PROTECTED]> writes: > > > On 1/21/07, Simon Riggs <[EMAIL PROTECTED]> wrote: > > >> - continue on error i.e. COMMIT can/might succeed - though there are > > >> still cases where it cannot, such as a serializable exception. > > > > > and what should be the behaviour of that? the same as rollback? > > > > The only conceivable implementation is an implicit savepoint issued > > before each statement. > > I'm not sure I agree here...before the NT implementation was changed > over to savepoint syntax it was perfectly possible to recover from > errors inside a transaction...and is still possible in plpgsql > functions only. What I'm asking for is to reopen this behavior > somehow...in the production environments I've worked in application > update and maintenance relied heavily on scripting, and lack of this > functionality forces me to wrap the script launch with C code to work > around limitations of the savepoint system.
Could you post an example, just so we're all clear what the problems are? I thought I understood what you are requesting; I may not. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
