Re: Cannot use a standalone backend to VACUUM in "postgres"" - Mailing list pgsql-general

From Manuel Sugawara
Subject Re: Cannot use a standalone backend to VACUUM in "postgres""
Date
Msg-id m3r6dhghvp.fsf@conexa.fciencias.unam.mx
Whole thread Raw
In response to Re: Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
List pgsql-general
Manuel Sugawara <masm@fciencias.unam.mx> writes:

> Alvaro Herrera <alvherre@commandprompt.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.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: tsvector_update_trigger throws error "column is not of tsvector type"
Next
From: "Markus Wollny"
Date:
Subject: Re: tsvector_update_trigger throws error "column is not of tsvector type"