Tom Lane wrote: > I think that it should be coded > to ignore ENOENT the same as the bgwriter does, and that it should press > on and keep trying to delete things even if it gets a failure.
Perhaps, if it gets ENOENT, record this fact -- and after rmtree returns, retry the whole thing. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
