From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | List pgsql-patches <pgsql-patches(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] Infrastructure changes for recovery |
Date: | 2008-09-18 12:18:00 |
Message-ID: | 1221740280.3913.2398.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Thu, 2008-09-18 at 09:05 +0100, Simon Riggs wrote:
> Feels like I should shutdown the bgwriter after recovery and then
> allow it to be cranked up again after normal processing starts, and do
> all of this through postmaster state changes. That way bgwriter
> doesn't need to do a dynamic state change.
This approach appears to be working nicely so far. Some ugly bits of
former patch removed.
Patch passes basic tests and changes state cleanly.
Restarting test cycle on this patch now, confirm tomorrow.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
Attachment | Content-Type | Size |
---|---|---|
recovery_infrastruc.v5.patch | text/x-patch | 36.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Glyn Astill | 2008-09-18 12:35:30 | Re: Regaining superuser access |
Previous Message | Heikki Linnakangas | 2008-09-18 12:17:18 | Re: optimizing CleanupTempFiles |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-18 13:06:36 | Re: [PATCHES] Infrastructure changes for recovery |
Previous Message | Simon Riggs | 2008-09-18 08:05:45 | Re: [PATCHES] Infrastructure changes for recovery |