Re: src/ports/pgcheckdir.c - Ignore dot directories... - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: src/ports/pgcheckdir.c - Ignore dot directories...
Date
Msg-id 20130214230704.GB2895@momjian.us
Whole thread Raw
In response to Re: src/ports/pgcheckdir.c - Ignore dot directories...  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: src/ports/pgcheckdir.c - Ignore dot directories...
List pgsql-hackers
On Tue, Feb  5, 2013 at 08:49:17AM -0500, Peter Eisentraut wrote:
> On 2/5/13 7:32 AM, Kevin Grittner wrote:
> > Sean Chittenden <sean@chittenden.org> wrote:
> >
> >> > Currently src/port/pgcheckdir.c will reject non-empty
> >> > directories, which is an issue during initdb(1) when PGDATA is
> >> > also the mount point for filesystems that support snapshots (e.g.
> >> > ZFS or UFS2).
> >> > Granted it's not hard to create a subdirectory, initdb there and
> >> > move the contents of the files around, it's extra work that
> >> > shouldn't be required.
> > I feel that it is very bad practice to use the mount point as the
> > PGDATA directory.  It forcloses a lot of reasonable actions that
> > someone managing the database server might want to take.
>
> Yes, a variant of this particular patch gets rejected about once every
> 18 months.

Agreed.  The attached patch modifies pg_check_dir() to report about
invisible and lost+found directory entries, and give more helpful
messages to the user.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

Attachment

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: BUG #7493: Postmaster messages unreadable in a Windows console
Next
From: Tomas Vondra
Date:
Subject: Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system