From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | "Graeme B(dot) Bell" <grb(at)skogoglandskap(dot)no> |
Cc: | Postgres Maillist <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: postgres hot-standby questions. |
Date: | 2015-03-26 18:48:33 |
Message-ID: | 8CFAFF7B-BD43-4481-89ED-DE1A3054B837@elevated-dev.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On Mar 26, 2015, at 12:42 PM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
>
> On Mar 26, 2015, at 12:17 PM, Graeme B. Bell <grb(at)skogoglandskap(dot)no> wrote:
>>
>> ...I won't be able to directly apply the (promoted) standby's new WAL entries over the top of it.
>
> I see--there's our difference. When I do this, I am willing to stay on the standby for a while if need be.
>
>> A checkpoint or autovacuum might generate a small change/entry in WAL (I don't know this for sure regarding autovacuum; this is a worst case assumption).
>
> I would think autovacuum would have to, since it writes some changes to at least index pages.
But you can disable autovacuum. And you can manually checkpoint. So maybe you'd just add that after shutting down services that access the db. (For me, that's mostly: "sudo launchctl unload my.particular.prefix.*")
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
From | Date | Subject | |
---|---|---|---|
Next Message | Graeme B. Bell | 2015-03-27 09:42:35 | Re: postgres hot-standby questions. |
Previous Message | Scott Ribe | 2015-03-26 18:42:28 | Re: postgres hot-standby questions. |