| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit could leave shared memory |
| Date: | 2008-04-17 12:30:12 |
| Message-ID: | 20080417123012.GB3846@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-04-17 13:03:18 | Re: Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory |
| Previous Message | Tom Lane | 2008-04-17 00:00:01 | pgsql: Repair two places where SIGTERM exit could leave shared memory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-04-17 12:34:52 | Re: Proposed patch - psql wraps at window width |
| Previous Message | Raphaël Jacquot | 2008-04-17 11:57:44 | Re: Submission of Feature Request : RFC- for Implementing Transparent Data Encryption in P |