| From: | "Mikko Partio" <dun(at)haisuli(dot)net> |
|---|---|
| To: | "Nico Sabbi" <nsabbi(at)officinedigitali(dot)it> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | |
| Date: | 2007-04-16 15:41:20 |
| Message-ID: | 59813.2001:14b8:1b0:0:216:d4ff:fe03:2af0.1176738080.squirrel@haisuli.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Nico Sabbi wrote:
>
>
> but "cp /tmp/pg//000000010000000000000021 pg_xlog/RECOVERYXLOG" looks
suspicious to me.
>
Works for me [clip from process listing]:
postgres 12864 12863 0 18:36 ? 00:00:00 cp
/wal/00000001000000E100000035 pg_xlog/RECOVERYXLOG
I think RECOVERYXLOG should be overwritten every time (the -l mode also
recreates RECOVERYXLOG link that points to the latest wal).
BTW thanks to Simon Riggs for pg_standby, it works very well!
Regards
MP
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-04-16 18:20:22 | Re: one more performance question I cannot test yet :( |
| Previous Message | Chris Browne | 2007-04-16 15:27:07 | Re: autovacuum vacuums entire database...is this right? |