Re: [PATCHES] Continue transactions after errors in psql - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PATCHES] Continue transactions after errors in psql
Date
Msg-id 200504260323.j3Q3Nr226246@candle.pha.pa.us
Whole thread Raw
In response to Re: [PATCHES] Continue transactions after errors in psql  (Mark Kirkwood <markir@paradise.net.nz>)
Responses Re: [PATCHES] Continue transactions after errors in psql  (Mark Kirkwood <markir@paradise.net.nz>)
List pgsql-hackers
Mark Kirkwood wrote:
> Bruce Momjian wrote:
> > 
> >     disable it by default for all sessions (current patch)
> >     enable it by default only for interactive sessions, like AUTOCOMMIT
> 
> These two seem like the best contenders.
> 
> The choice comes down to whether we should:
> 
> 1) Be like most other dbms's (e.g. Oracle, Firebird) + follow the spec.
> 2) Minimize psql behavior changes for current postgresql users.
> 
> 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.  The fact that
interactive and non-interactive behavior is different is something that
suggests that turning it on by default might cause confusion.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: [PATCHES] Continue transactions after errors in psql
Next
From: "Qingqing Zhou"
Date:
Subject: Re: simplify register_dirty_segment()