Tom Lane wrote:
Lou Picciano loupicci...@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
TL == Tom Lane t...@sss.pgh.pa.us writes:
TL Here is the problem: what if someday that filesystem happens not to
TL be mounted? Then you have a bare mountpoint directory, with no real
TL way for the postmaster to notice that that wasn't what you intended.
TL Hilarity ensues.
That is a
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
A symbolic link seems both safer and easier.
The notion of mounting a filesystem directly there scares me, on
the whole. Here is the problem: what if someday that filesystem
happens not to be mounted?
TL == Tom Lane t...@sss.pgh.pa.us writes:
TL It *is* configurable: make pg_xlog a symlink.
I notice that everyone suggests using a symlink, but I never see anyone
suggest just mounting a filesystem there.
Is there a (technical) reason for that? Or is a symlink just though to
be easier to
James Cloos cl...@jhcloos.com wrote:
I notice that everyone suggests using a symlink, but I never see
anyone suggest just mounting a filesystem there.
I think initdb wants an empty directory. Once it creates the
directory structure with pg_xlog, if that's a mount point, it's a
bit awkward
On 11/22/10 10:42 AM, James Cloos wrote:
TL == Tom Lanet...@sss.pgh.pa.us writes:
TL It *is* configurable: make pg_xlog a symlink.
I notice that everyone suggests using a symlink, but I never see anyone
suggest just mounting a filesystem there.
Is there a (technical) reason for that? Or
Kevin Grittner kevin.gritt...@wicourts.gov writes:
James Cloos cl...@jhcloos.com wrote:
I notice that everyone suggests using a symlink, but I never see
anyone suggest just mounting a filesystem there.
I think initdb wants an empty directory. Once it creates the
directory structure with
Admin Friends, Can someone tell me the conf variablee to change location of
binary logs? Would like to store logs in a location other than pg_xlog in
cluster data dir.
Thanks, Lou
Lou Picciano loupicci...@comcast.net writes:
Admin Friends, Can someone tell me the conf variablee to change location of
binary logs? Would like to store logs in a location other than pg_xlog in
cluster data dir.
There is no such setting. But if you're so inclined you can make
pg_xlog be a
-admin pgsql-admin@postgresql.org
Sent: Sunday, November 21, 2010 7:54:55 PM
Subject: Re: [ADMIN] binary logs: a location other than pg_xlog??
Lou Picciano loupicci...@comcast.net writes:
Admin Friends, Can someone tell me the conf variablee to change location of
binary logs? Would like
loupicci...@comcast.net
Cc: pgsql-admin pgsql-admin@postgresql.org
Sent: Sunday, November 21, 2010 7:54:55 PM
Subject: Re: [ADMIN] binary logs: a location other than pg_xlog??
Lou Picciano loupicci...@comcast.net writes:
Admin Friends, Can someone tell me the conf variablee to change
...@sss.pgh.pa.us, pgsql-admin pgsql-admin@postgresql.org
Sent: Sunday, November 21, 2010 10:21:20 PM
Subject: Re: [ADMIN] binary logs: a location other than pg_xlog??
On Mon, 2010-11-22 at 03:09 +, Lou Picciano wrote:
Really? Wouldn't it be good general practice to store the xlogs on a
different
Lou Picciano loupicci...@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
13 matches
Mail list logo
