Re: [PATCHES] Continue transactions after errors in psql

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Continue transactions after errors in psql
Date: 2005-04-26 05:54:34
Message-ID: 426DD79A.10808@paradise.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian wrote:
> Mark Kirkwood wrote:
>
>
>>Personally I favor 1), so would prefer:
>>
>>enable it by default only for interactive sessions, like AUTOCOMMIT
>
>
> We are going for 'off' by default and only interactive.

Sweet.

> The fact that
> interactive and non-interactive behavior is different is something that
> suggests that turning it on by default might cause confusion.
>

True, but reasonably explained by suggesting that non-interactive
scripts should not be expected to keep going when there are typos or
similar. In fact, I seem to recall being burned by that very thing in my
early Oracle days...

Mark

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-04-26 06:00:52 Re: DO INSTEAD and conditional rules
Previous Message Tom Lane 2005-04-26 05:32:35 Re: simplify register_dirty_segment()

Browse pgsql-patches by date

  From Date Subject
Next Message Greg Sabino Mullane 2005-04-26 11:43:31 Re: [HACKERS] Continue transactions after errors in psql
Previous Message Bruce Momjian 2005-04-26 03:23:53 Re: [PATCHES] Continue transactions after errors in psql