Andres Freund <and...@2ndquadrant.com> writes: > On 2014-07-22 10:17:15 -0400, Tom Lane wrote: >> Or even more to the point, investigate why it's there in the first >> place; perhaps there's an actual fixable bug somewhere in there.
> I think MauMau's scenario of a failover to another database explains > their existance - there's no step that'd remove them after promoting a > standby. > So there indeed is a need to have a sensible mechanism for removing them > at some point. But it should be about removing, not ignoring them. Agreed. Note that RemovePgTempFiles, as such, only reclaims disk space. It does not clean out the pg_class entries, which means that just running that at standby promotion would do nothing to get rid of autovacuum's whining. 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