Re: Shouldn't we document "don't use a mountpoint as $PGDATA"?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Shouldn't we document "don't use a mountpoint as $PGDATA"?
Date: 2015-09-02 00:25:27
Message-ID: 20150902002527.GF27332@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 1, 2015 at 08:20:47PM -0400, Bruce Momjian wrote:
> On Tue, Jul 28, 2015 at 02:19:00PM -0400, Andrew Dunstan wrote:
> >
> > On 07/28/2015 02:01 PM, Tom Lane wrote:
> > >I had a discussion with some folks at Red Hat about this:
> > >https://bugzilla.redhat.com/show_bug.cgi?id=1247477
> > >
> > >I had the idea that we had documented somewhere that the data directory
> > >should not be a filesystem mount point, but I sure can't find it now.
> > >Any objections to adding some text about this to section 17.2, near the
> > >caveats about NFS?
> >
> >
> >
> > Please do. I came across a client who should have known better doing
> > this just a week or two ago.
>
> Uh, we added an initdb warning about mount points:
>
> commit 17f15239325a88581bb4f9cf91d38005f1f52d69
> Author: Bruce Momjian <bruce(at)momjian(dot)us>
> Date: Sat Feb 16 18:52:50 2013 -0500
>
> Warn about initdb using mount-points
>
> Add code to detect and warn about trying to initdb or create pg_xlog on
> mount points.
>
> Was that not sufficient?

Oh, I see in the commit message you knew about the initdb warning ---
never mind.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-09-02 00:39:03 Re: Fwd: Core dump with nested CREATE TEMP TABLE
Previous Message Bruce Momjian 2015-09-02 00:20:47 Re: Shouldn't we document "don't use a mountpoint as $PGDATA"?