| 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-27 14:45:35 |
| Message-ID: | 15DE9D30-40C4-402D-89AC-F7787214D765@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mar 27, 2015, at 3:46 AM, Graeme B. Bell <grb(at)skogoglandskap(dot)no> wrote:
>
> For example: in the processes that you were using prior to our conversation, which you mentioned before (shutting down services before server), were you already doing a forced checkpoint to counter archive_timeout, and had you disabled autovacuum?
No. because I run on the newly-promoted master for a while, then rsync back. So all I care about is getting all committed transactions replicated.
--
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 | naveen kumar | 2015-03-28 00:33:39 | postgres log_destination question |
| Previous Message | Graeme B. Bell | 2015-03-27 09:46:10 | Re: postgres hot-standby questions. |