| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | StartupCLOG |
| Date: | 2008-09-04 08:37:27 |
| Message-ID: | 1220517447.4371.852.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I notice that StartupCLOG zeroes out entries later than the nextxid when
we complete recovery in StartupXLOG, reason given is safety in case we
crash.
ISTM that we should also do that whenever we see a Shutdown Checkpoint
in WAL, since that can be caused by a shutdown immediate, shutdown abort
or crash. In each of those cases its possible that we would have the
same conditions as exist at the end of WAL.
Can't see a failure case of importance though, just wanted to flag it up
as a possible. Better a false positive with these types of concern.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2008-09-04 08:53:03 | Re: Conflict resolution in Multimaster replication(Postgres-R) |
| Previous Message | Heikki Linnakangas | 2008-09-04 08:07:19 | Re: New FSM patch |