| From: | "Mario Weilguni" <mweilguni(at)sime(dot)com> |
|---|---|
| To: | <shridhar_daithankar(at)persistent(dot)co(dot)in>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_xlog question |
| Date: | 2003-08-06 07:56:32 |
| Message-ID: | 001101c35bf0$40f6f170$1e01c00a@icomedias.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > If you could replicate/rsync pg_xlog to another machine, you could get
it
> > correctly in case of failover.
>
> Argh.. I forgot.. Simple option is to sync the pg_xlog while doing
failover. It
> might add some 10 odd sec to failover process but should be bullet proof..
>
> I don't know if PG is nose poking about permissions of those files.
otheriwse
> it might refuse to start.. Check out..
>
> Worth adding to failover HOWTO. I doubt if one exists for postgresql.
Thanks for the response, but syncing pg_xlog separatly (without DRBD device)
is useless, because a failover will take place when there's an error, so the
extra sync of pg_xlog is very likely to fail.
Regards,
Mario Weilguni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sander Steffann | 2003-08-06 09:08:51 | Re: Changing DB ownership |
| Previous Message | Peter Eisentraut | 2003-08-06 07:52:07 | Re: plPHP -- sort of an announcement.. but not commercial |