| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca> |
| 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:45:45 |
| Message-ID: | 40987179.3070407@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
> 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?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-05 04:48:48 | pgsql-server/ oc/src/sgml/ref/alter_table.sgml ... |
| Previous Message | Rod Taylor | 2004-05-05 04:41:14 | Re: Multiple Xids in PGPROC? |