Re: [PATCHES] Continue transactions after errors in psql

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
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 03:23:53
Message-ID: 200504260323.j3Q3Nr226246@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Qingqing Zhou 2005-04-26 03:27:55 Re: simplify register_dirty_segment()
Previous Message Mark Kirkwood 2005-04-26 03:08:59 Re: [PATCHES] Continue transactions after errors in psql

Browse pgsql-patches by date

  From Date Subject
Next Message Mark Kirkwood 2005-04-26 05:54:34 Re: [PATCHES] Continue transactions after errors in psql
Previous Message Mark Kirkwood 2005-04-26 03:08:59 Re: [PATCHES] Continue transactions after errors in psql