| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Goulet, Dick" <DGoulet(at)vicr(dot)com>, <mkl(at)webde-ag(dot)de> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Multiple WALs for PITR ? |
| Date: | 2004-10-07 20:58:24 |
| Message-ID: | NOEFLCFHBPDAFHEIPGBOCENECFAA.simon@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>Goulet, Dick
> As an Oracle DBA primarily, moving more towards PostGreSQL as time
> passes, the "alter system switch logfile" command is very often used at
> the end of a hot backup to force a logfile switch and consequently
> provide a full archive log set. The command causes the database engine
> to cease using the current online redo log and have it archived to the
> archive log destination. This is the only way to be sure that all
> required archive logs are present in a backup to reconstitute the
> database at another location.
>
Yep, know what it does - just wanted to check that people really used it.
I always felt I did that as a precaution rather than for good reason.
OK - 8.1 it is then,
Best Regards
Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sharon Schooley | 2004-10-07 23:28:26 | High Availability for PostgreSQL |
| Previous Message | admin | 2004-10-07 18:44:21 | Re: problems with pg_dump and pg_restore |