| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Streaming Replication and archiving |
| Date: | 2010-01-19 22:13:36 |
| Message-ID: | 4B562E90.3080107@catalyst.net.nz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've been having a look at this, one master + one replica and also one
master + 2 replicas. I gotta say this is a nice piece of functionality
(particularly the multiple replicas).
I've been using the wiki page
(http://wiki.postgresql.org/wiki/Streaming_Replication) as a guide, and
I notice that it recommends the master (and replicas) have a non-trivial
archive_command even after the backup step is completed. ISTM that after
the backup the master's archive_command can be set to '' or '/bin/true'
as the walsender does not make any use of the WAL archive (AFAICS
anyway). Clearly it might be desirable to have the archived segments
around for other reasons - but equally it might be desirable *not* to
have to have to (e.g disk space), or am I overlooking something?
Cheers
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-01-19 22:14:31 | Re: MySQL-ism help patch for psql |
| Previous Message | Mark Kirkwood | 2010-01-19 22:06:56 | Streaming Replication and archiving |