Re: Cannot use a standalone backend to VACUUM in "postgres""

From: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Cannot use a standalone backend to VACUUM in "postgres""
Date: 2008-04-08 03:11:54
Message-ID: m3r6dhghvp.fsf@conexa.fciencias.unam.mx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> writes:

> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>
>> Hi Manuel,
>
> Hi Alvaro!
>
>> I suggest you look for temp tables that have not been reclaimed.
>> We've had a couple of reports where leftover temp tables have
>> stopped the frozen-xid counter from advancing. (They would have a
>> very old relfrozenxid.)
>
> Thank you very much for the suggestion. Any pointers on how to do
> that? A quick serch in google didn't show anything relevant.

Will look into pg_class, of course. Somehow I was thinking something
else. Thanks again.

Regards,
Manuel.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Markus Wollny 2008-04-08 03:40:33 Re: tsvector_update_trigger throws error "column is not of tsvector type"
Previous Message Tom Lane 2008-04-08 02:47:22 Re: tsvector_update_trigger throws error "column is not of tsvector type"