Re: Streaming Replication and archiving - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Streaming Replication and archiving
Date
Msg-id 4B57B266.2050209@agliodbs.com
Whole thread Raw
In response to Re: Streaming Replication and archiving  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Streaming Replication and archiving  (Fujii Masao <masao.fujii@gmail.com>)
Re: Streaming Replication and archiving  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
> Huh?  *Archived* segments aren't supposed to get deleted, at least not
> by any automatic Postgres action.  It would be up to the DBA how long
> he wants to keep them around.

OK.  The docs indicated that the segments needed to be kept around in
case the slave fell behind.  If that's not the case (as it appears not
to be) then they can just be deleted by cron job, or the archive_command
on the master can be changed.

Presumably, however, if the slave falls sufficiently behind and there
are no archive logs, then the slave would not be able to resynch with
the master, no?

--Josh Berkus



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: HS/SR and smart shutdown
Next
From: Robert Haas
Date:
Subject: Re: HS/SR and smart shutdown