Postgres Pro
Downloads
Home   >   mailing lists

Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit could leave shared memory - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit could leave shared memory
Date
Msg-id 20080417123012.GB3846@alvh.no-ip.org
Whole thread Raw
Responses Re: Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
Tree view 
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.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Lessons from commit fest
Next
From: Peter Eisentraut
Date:
Subject: get rid of psql welcome message