| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XLogArchivingActive |
| Date: | 2006-05-27 11:51:50 |
| Message-ID: | 44783D56.3000405@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim C. Nasby wrote:
>
> Also, regarding needing to place an archiver command in
> pg_start_backup_online, another option would be to depend on the
> filesystem backup to copy the WAL files, and just let them pile up in
> pg_xlog until pg_stop_backup_online. Of course, that would require a
> two-step filesystem copy, since you'd need to first copy everything in
> $PGDATA, and then copy $PGDATA/pg_xlog after you have that.
Sounds fine. This solves the problem to insure that all required wal
files are actually copied to the wal archive.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2006-05-27 11:52:52 | Re: Inefficient bytea escaping? |
| Previous Message | Marko Kreen | 2006-05-27 11:15:41 | Re: Inefficient bytea escaping? |