| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "James Sewell *EXTERN*" <james(dot)sewell(at)lisasoft(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: WAL archive on slave |
| Date: | 2014-02-10 09:30:36 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17CA45E1@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
James Sewell wrote:
> If it is the the only way that I could achieve what I wanted would be to set
> wal_keep_segments high enough then they will all be archived on promotion?
Even if you set wal_keep_segments high I don't think that the replayed
WAL will be archived.
> I'm still not sure why they wouldn't be archived on the slave, seen as they show up in the directory?
> Is there a limitation I'm not thinking about here?
I guess that the idea is that a cluster will only archive the WAL it
generates. Typically, the primary would archive these (if you don't archive
WAL on the primary, you're probably doing something wrong).
So this would only lead to duplicates.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glyn Astill | 2014-02-10 11:40:56 | Re: Better Connection Statistics |
| Previous Message | Peter Geoghegan | 2014-02-10 06:15:21 | Re: Xlogdump compiling error : undefined reference to `ber_sockbuf_io_udp' |