| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Simplifying replication |
| Date: | 2010-10-27 17:37:24 |
| Message-ID: | 4CC86354.8070501@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> It is the same to the user either way. In either case you have to
>> change some settings and restart the master.
>
> Except that changing wal_keep_segments doesn't require restarting the master.
Our docs say that it does:
This parameter can only be set in the postgresql.conf file or on the
server command line.
http://www.postgresql.org/docs/9.0/static/runtime-config-wal.html#RUNTIME-CONFIG-REPLICATION
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2010-10-27 17:48:35 | Re: Postgres insert performance and storage requirement compared to Oracle |
| Previous Message | Josh Berkus | 2010-10-27 17:05:11 | Re: max_wal_senders must die |