pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Lou Picciano <loupicciano@comcast.net>
Cc: jd@commandprompt.com
Cc: James Cloos <cloos@jhcloos.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: binary logs: a location other than pg_xlog??
Date: Tue, 23 Nov 2010 13:54:15 -0600
Message-ID: <4CEBC7870200002500037D94@gw.wicourts.gov> (raw)
In-Reply-To: <14940.1290453941@sss.pgh.pa.us>
References: <1557390103.902044.1290397034758.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net>
	<4788.1290402707@sss.pgh.pa.us>
	<4788.1290402707@sss.pgh.pa.us>
	<m3vd3p2o9l.fsf@jhcloos.com>
	<4CEA69F30200002500037D0B@gw.wicourts.gov>
	<4CEA69F30200002500037D0B@gw.wicourts.gov>
	<14940.1290453941@sss.pgh.pa.us>

Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <Kevin.Grittner@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?  Then you have a bare mountpoint
> directory, with no real way for the postmaster to notice that that
> wasn't what you intended.  Hilarity ensues.
 
Yeah, we've experienced that in our shop with backup mount points --
so it was not quite so hilarious as live database directories, but
funny enough from a space utilization perspective.  We've taken to
ensuring that the subdirectory used as a mount point is locked down
to a root:root owner with no rights granted.  Since we don't do our
backups as the root user, failure to mount (or to mount in time)
generates understandable errors in a timely fashion.  I still much
prefer a symlink for pg_xlog, but I thought that this suggestion
might save someone some pain.
 
> don't symlink to exactly the filesystem mount point but rather a
> directory level or two down, so that the target dir is not there
> if the mount fails.
 
Good point.  We have done it that way, but primarily for another
reason -- we often have more than one database cluster running on
the machine, and we generally have them share an xlog filesystem.
 
-Kevin



view thread (13+ messages)  latest in thread

Message-ID: <4CEBC7870200002500037D94@gw.wicourts.gov>
Permalink:  ../4CEBC7870200002500037D94@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4CEBC7870200002500037D94@gw.wicourts.gov

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, tgl@sss.pgh.pa.us, loupicciano@comcast.net, jd@commandprompt.com, cloos@jhcloos.com
  Subject: Re: binary logs: a location other than pg_xlog??
  In-Reply-To: <4CEBC7870200002500037D94@gw.wicourts.gov>
  References: <1557390103.902044.1290397034758.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> <4788.1290402707@sss.pgh.pa.us> <m3vd3p2o9l.fsf@jhcloos.com> <4CEA69F30200002500037D0B@gw.wicourts.gov> <14940.1290453941@sss.pgh.pa.us> <4CEBC7870200002500037D94@gw.wicourts.gov>

* 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