Re: PG in container w/ pid namespace is init, process exits cause restart - Mailing list pgsql-hackers

From Joe Conway
Subject Re: PG in container w/ pid namespace is init, process exits cause restart
Date
Msg-id 5aef7eed-613c-4423-568c-38442d8f1ae7@joeconway.com
Whole thread Raw
In response to Re: PG in container w/ pid namespace is init, process exits cause restart  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5/4/21 1:43 PM, Tom Lane wrote:
> Greg Stark <stark@mit.edu> writes:
>> On Mon, 3 May 2021 at 15:44, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> BTW, as far as that goes, I think the general recommendation is that
>>> the datadir shouldn't be a mount point, because bad things happen if
>>> you mount or unmount the drive while the postmaster is up.  I could
>>> see enforcing that, if we could find a reasonably platform-independent
>>> way to do it.
> 
>> I don't think the problem is unmounting -- on BSD you have to try
>> really hard to unmount filesystems that have files open on them and
>> afaik you can't do it on Linux at all (which I still claim is the
>> original sin that led to the fsync issues).
>> The problem was mounting filesystems if it happened late -- ie. After
>> Postgres had started up. It was exacerbated by some startup scripts
>> that would automatically run initdb if there was nothing present.
> 
> Yeah, at least that was the case that somebody (Joe Conway if memory
> serves) reported years ago.


Guilty as charged ;-)

Joe
-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PG in container w/ pid namespace is init, process exits cause restart
Next
From: Mark Dilger
Date:
Subject: Re: Extending amcheck to check toast size and compression