| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Kempter <kevin(at)kevinkempterllc(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Understanding wal segments |
| Date: | 2007-11-02 05:38:48 |
| Message-ID: | 22325.1193981928@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Kevin Kempter <kevin(at)kevinkempterllc(dot)com> writes:
> Also I suspect after each filesystem backup I should remove the older
> archived segments since the file system backup makes them
> irrelevant. Is this accurate?
Depends what your goals are. If you only want to be able to recover
the latest database state then you only need archived WAL segments
back to the start of the latest filesystem backup. If you are
interested in the "PITR" aspect of it --- being able to revert back
to last Tuesday before some bad guy injected bad data, say --- then
you'll want to keep older filesystem backups too, and a continuous
string of archived WAL files covering the period of interest.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Kempter | 2007-11-02 05:50:00 | Re: Understanding wal segments |
| Previous Message | Kevin Kempter | 2007-11-02 05:38:13 | Re: Understanding wal segments |