Simon Riggs <si...@2ndquadrant.com> writes: > Thus there is no guarantee that this is sufficient to have archived all > the files you would like to archive. The patch does not provide a clean > shutdown in all cases and since you don't know what state its in, you > are still forced to take external action to be safe, exactly as you do > already.
> If I didn't already say, I came up with exactly the same solution 2 > years ago and then later explained it didn't work in all cases. I'm > saying the same thing again here now. What's your point? Surely the applied patch is a *necessary* component of any attempt to try to ensure archiving is complete at shutdown. I agree that it doesn't cover every risk factor, and there are some risk factors that cannot be covered by Postgres itself. But isn't it a step in a desirable direction? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers