| From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
|---|---|
| To: | Devrim GUNDUZ <devrim(at)CommandPrompt(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Shared pg_xlog directory/partition and warm standby |
| Date: | 2006-11-27 13:17:44 |
| Message-ID: | 456AE578.6010807@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Devrim GUNDUZ wrote:
> Hello,
>
> Is there anything that may prevent two PostgreSQL servers to share the
> same pg_xlog directory; while one is using read-only and the other one
> is using the same partition for read and write? The problem is: If we
> share the same pg_xlog between production server and warm standby
> server; can you see any possibility of data/xlog corruption? Of course,
> warm standby server will mount that partition as read-only.
What happens in the standby server falls so far behind the master that
the xlogs it wants to read are already being overwritten?
AFAIK the files in pg_xlog form a circular buffer, and are reused after
a while...
greetings, Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-11-27 14:11:18 | Re: Integrating Replication into Core |
| Previous Message | Florian G. Pflug | 2006-11-27 13:10:09 | Re: "Optional ident" authentication |