Re: Is autovacuum too noisy about orphan temp tables?

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is autovacuum too noisy about orphan temp tables?
Date: 2008-10-14 13:07:52
Message-ID: 20081014220046.545B.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> > LOG: autovacuum: found orphan temp table "pg_temp_2"."foo" in database
> > "postgres"
>
> What else would you do? I can't see adding state to remember when we
> printed it last.

Why can't we drop orphan temp tables automatically?

> > Also, it doesn't give me any hint
> > on what I can do to get rid of the message; I had to search the archives
> > to find out that I can "DROP SCHEMA pg_temp_2".
>
> We could surely add an errhint() to the message.

Standard DBAs are blind to LOG level messages. If the message is important,
we should use WARNING level. Monitoring middleware notifies DBAs of
WARNING or higher messages, but discards LOG or lower messages.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-10-14 13:33:21 Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED
Previous Message Tom Lane 2008-10-14 12:51:06 Re: Is autovacuum too noisy about orphan temp tables?