> -----Original Message-----
> From: Tom Lane
>
> I have just sent to the pgsql-patches list a rather large set of
> proposed diffs for the WAL code. These changes:
>
> * Store two past checkpoint locations, not just one, in pg_control.
> On startup, we fall back to the older checkpoint if the newer one
> is unreadable. Also, a physical copy of the newest checkpoint record
> is kept in pg_control for possible use in disaster recovery (ie,
> complete loss of pg_xlog). Also add a version number for pg_control
> itself. Remove archdir from pg_control; it ought to be a GUC
> parameter, not a special case (not that it's implemented yet anyway).
>
Is archdir really a GUC parameter ?
Regards,
Hiroshi Inoue
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
- [HACKERS] Proposed WAL changes Tom Lane
- Re: [HACKERS] Proposed WAL changes Hiroshi Inoue
- Re: [HACKERS] Proposed WAL changes Tom Lane
- Re: [HACKERS] Proposed WAL changes Christopher Masto
- Re: [HACKERS] Proposed WAL changes Vadim Mikheev
- Re: [HACKERS] Proposed WAL changes Tom Lane
- Re: [HACKERS] Proposed WAL changes Nathan Myers
- Re: [HACKERS] Proposed WAL changes The Hermit Hacker
- Re: [HACKERS] Proposed WAL changes Ian Lance Taylor
- RE: [HACKERS] Proposed WAL changes Mikheev, Vadim
- RE: [HACKERS] Proposed WAL changes Alex Pilosov
- Re: [HACKERS] Proposed WAL changes Nathan Myers