Re: binary logs: a location other than pg_xlog?? - Mailing list pgsql-admin

From Tom Lane
Subject Re: binary logs: a location other than pg_xlog??
Date
Msg-id 4788.1290402707@sss.pgh.pa.us
Whole thread Raw
In response to Re: binary logs: a location other than pg_xlog??  (Lou Picciano <loupicciano@comcast.net>)
Responses Re: binary logs: a location other than pg_xlog??  (James Cloos <cloos@jhcloos.com>)
Re: binary logs: a location other than pg_xlog??  (Bruce Momjian <bruce@momjian.us>)
List pgsql-admin
Lou Picciano <loupicciano@comcast.net> writes:
> Sure - of course - performance, too! It just seems like such an obvious candidate for a configurable option; I'm a
bitsurprised it isn't in there... L  

It *is* configurable: make pg_xlog a symlink.  The reason we don't
handle this via postgresql.conf is that you could too easily shoot
yourself in the foot by breaking the link between a data directory
and its xlogs.  There are no postgresql.conf entries that say
destroy_all_my_data_immediately_please = on
but that's more or less what an easily changeable pg_xlog pointer
would be.

In short: this is not something to change if you don't know what
you're doing.  If you do, you should be able to handle it using
the mechanism provided.

            regards, tom lane

pgsql-admin by date:

Previous
From: Lou Picciano
Date:
Subject: Re: binary logs: a location other than pg_xlog??
Next
From: Lukasz Brodziak
Date:
Subject: Re: Zeroing single tuple in data file.