Can autovacuum just set a flag on the orphaned temp table's pg_class
record indicating it's been determined to be an orphan? Then other
tools could easily list orphaned tables and offer to delete them.
greg
On 15 Oct 2008, at 10:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Robert Haas" <robertmhaas@gmail.com> writes:
>> A much better solution would be to not print the warning every time.
>> I think the right solution is to do exactly what you rejected
>> upthread, namely adding some kind of stack to track the last time
>> this
>> was printed.
>
> I really doubt that the problem is worth so much effort. Your
> handwavy
> solution doesn't work, I think, because you are ignoring the problem
> that this code is executed in relatively short-lived processes that
> aren't all examining the same database. By the time you got to a
> solution that did work it'd be pretty complicated.
>
> 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