| 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 03:08:59 |
| Message-ID: | 426DB0CB.9040204@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-04-26 03:23:53 | Re: [PATCHES] Continue transactions after errors in psql |
| Previous Message | Bruce Momjian | 2005-04-26 03:01:50 | Re: [HACKERS] PostgreSQL pam ldap document |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-04-26 03:23:53 | Re: [PATCHES] Continue transactions after errors in psql |
| Previous Message | Alvaro Herrera | 2005-04-26 03:04:45 | Re: Shared dependency patch |