From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | 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 04:41:14 |
Message-ID: | 1083732074.54823.15.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2004-05-05 at 00:45, Christopher Kings-Lynne 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.
>
> Point there being "main transaction". What i'm saying is that the vast
> majority of your "transactions" will be single statements. eg. single
> selects, single updates, etc.
Actually, they're not. A vast majority of my transactions are over 5
statements -- each of which is eagerly anticipating being wrapped in a
subtransaction.
> > In fact, I would be surprised if tools like psql went very long without
> > doing the same thing so users can recover from spelling mistakes.
>
> If the user does an explicit BEGIN, then perhaps we might, but how often
> does the user do an explicit BEGIN?
What user? Users aren't allowed in production. Strictly code.
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-05-05 04:45:45 | Re: Multiple Xids in PGPROC? |
Previous Message | Rod Taylor | 2004-05-05 04:30:23 | Re: Multiple Xids in PGPROC? |