From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lou Picciano <loupicciano@comcast.net>
Cc: jd@commandprompt.com, pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: binary logs: a location other than pg_xlog??
Date: Mon, 22 Nov 2010 00:11:47 -0500
Message-ID: <4788.1290402707@sss.pgh.pa.us> (raw)
In-Reply-To: <1557390103.902044.1290397034758.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net>
References: <1557390103.902044.1290397034758.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net>
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 bit surprised 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, loupicciano@comcast.net
Subject: Re: binary logs: a location other than pg_xlog??
In-Reply-To: <4788.1290402707@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox