| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | hstenger(at)ieee(dot)org |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Managing Rollback |
| Date: | 2000-07-31 19:31:24 |
| Message-ID: | 10341.965071884@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
hstenger(at)adinet(dot)com(dot)uy writes:
> What do we mean in the last two lines of the following comment?
> /* ----------------
> * Here we are in the middle of a
> transaction block but
> * one of the commands caused an abort so
> we do nothing
> * but remain in the abort state.
> Eventually we will get
> * to the "END TRANSACTION" which will set
> things straight.
> * ----------------
> */
> case TBLOCK_ABORT:
It just means that nothing's going to happen until the user sends
COMMIT or ROLLBACK --- the xact.c state will remain the same until
then.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-07-31 23:31:13 | Announcement: I'm joining Great Bridge |
| Previous Message | hstenger | 2000-07-31 18:53:33 | Managing Rollback |