| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql-server: Fix a number of places where brittle data structures or |
| Date: | 2004-09-07 15:19:29 |
| Message-ID: | 200409071119.29856.xzilla@users.sourceforge.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Monday 06 September 2004 19:34, Tom Lane wrote:
> Log Message:
> -----------
> Fix a number of places where brittle data structures or overly strong
> Asserts would lead to a server core dump if an error occurred while
> trying to abort a failed subtransaction (thereby leading to re-execution
> of whatever parts of AbortSubTransaction had already run). This of course
> does not prevent such an error from creating an infinite loop, but at
> least we don't make the situation worse. Responds to an open item on
> the subtransactions to-do list.
>
Does that eliminate the following from the open items list?
resolve issues with pg_subtrans and pg_clog re: WAL-logging and fsync /
determine proper crash recovery/logging for pg_subtrans
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-09-07 15:33:15 | Re: pgsql-server: Fix a number of places where brittle data structures or |
| Previous Message | Tom Lane | 2004-09-07 14:32:28 | pgsql-server: Fix places where WaitForxxx can block, to eliminate |