Re: Re: [COMMITTERS] pgsql: Repair two places whereSIGTERM exit couldleave shared memory - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Re: [COMMITTERS] pgsql: Repair two places whereSIGTERM exit couldleave shared memory
Date
Msg-id 48074D25.8010709@enterprisedb.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Re: [COMMITTERS] pgsql: Repair two places whereSIGTERM exit couldleave shared memory  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
Alvaro Herrera wrote:
> Heikki Linnakangas wrote:
>> Alvaro Herrera wrote:
>>> Tom Lane wrote:
>>>
>>>> Also use this method
>>>> for createdb cleanup --- that wasn't a shared-memory-corruption problem,
>>>> but SIGTERM abort of createdb could leave orphaned files lying around.
>>> I wonder if we could use this mechanism for cleaning up in case of
>>> failed CLUSTER, REINDEX or the like.  I think these can leave dangling
>>> files around.
>> They do clean up on abort or SIGTERM.
> 
> Ah, we're OK then.

Wait, my memory failed me! No, we don't clean up dangling files on 
SIGTERM. We should...

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory
Next
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Repair two places whereSIGTERM exit couldleave shared memory