| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | joe(at)mcknight(dot)de, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "recovering prepared transaction" after serverrestart message |
| Date: | 2006-11-03 14:42:02 |
| Message-ID: | 1886.1162564922@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> We only care when they break, otherwise its just situation normal, yes?
No, the trouble case is where the XA manager that owns the transaction
has forgotten about it.
> Is there a way to see prepared transactions where the original session
> that prepared then has died? Perhaps the message at startup should be
> "you have at least one prepared transaction that needs resolution".
I am completely baffled by this focus on database startup time. That's
not where the problem is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2006-11-03 15:06:50 | Re: "recovering prepared transaction" after serverrestart message |
| Previous Message | Simon Riggs | 2006-11-03 08:06:55 | Re: "recovering prepared transaction" after serverrestart message |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2006-11-03 15:06:50 | Re: "recovering prepared transaction" after serverrestart message |
| Previous Message | Alvaro Herrera | 2006-11-03 13:45:04 | Re: [PATCHES] WAL logging freezing |