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. 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. It's not limited
to utility commands like that either: if you create a table and copy a
few gigabytes of data into it in a transaction, and crash before
committing, you're left with a dangling file as well.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
