Re: Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory |
| Дата | |
| Msg-id | 20080417130543.GF3846@alvh.no-ip.org обсуждение |
| Ответ на | Re: Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit couldleave shared memory (Heikki Linnakangas <heikki@enterprisedb.com>) |
| Ответы |
Re: Re: [COMMITTERS] pgsql: Repair two places whereSIGTERM
exit couldleave shared memory
|
| Список | pgsql-hackers |
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. > If you experience a sudden power loss, or kill -9 while CLUSTER or > REINDEX is running, they will leave behind dangling files, but that's > a different problem. Sure, no surprises there. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: