| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Miguel Arroz <arroz(at)guiamac(dot)com> |
| Cc: | Steve Poe <steve(dot)poe(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Planning hot/live backups? |
| Date: | 2008-03-25 04:50:41 |
| Message-ID: | 47E884A1.3010407@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Miguel Arroz wrote:
> Going a bit off topic, but one quick question: to avoid storing GB of
> WAL files that will probably take a lot of time to reload, how can the
> backup be "reset"? I suspect that it's something like stopping the WAL
> archiving, doing a new base backup, and restart archiving, but I've
> never done it (have been using SQL dumps), so...
Basically, you only need WAL logs from the last time you made a back-up
of your data directory. We do nightly re-rsync of our data directory
and then purge old WAL files that are no longer needed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sathiya psql | 2008-03-25 08:35:20 | postgresql is slow with larger table even it is in RAM |
| Previous Message | Chris | 2008-03-25 04:18:00 | Re: slow pg_connect() |