| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Multiple Xids in PGPROC? |
| Date: | 2004-05-05 22:07:33 |
| Message-ID: | 1083794852.3028.6.camel@stromboli |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2004-05-05 at 05:30, Rod Taylor wrote:
> Yup.. And some of us intend on wrapping every single statement in a
> subtransaction so we can rollback on an error without aborting the main
> transaction.
>
That is exactly what is needed to achieve full Oracle & DB2
compatibility.
I suggest that this should be a session settable parameter, to allow
session transaction semantics to mimic particular DBMS.
I want the behaviour but not the effort...
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-05-05 22:08:15 | Re: Multiple Xids in PGPROC? |
| Previous Message | Joshua D. Drake | 2004-05-05 21:23:03 | Re: PostgreSQL pre-fork speedup |