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

From Alvaro Herrera
Subject Re: Cannot use a standalone backend to VACUUM in "postgres""
Date
Msg-id 20080408222155.GU9062@alvh.no-ip.org
Whole thread Raw
In response to Re: Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
Responses Re: Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
List pgsql-general
Manuel Sugawara wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
>
> > Hmm, nope -- take away the relnamespace check, because there is a
> > different namespace for each backend (pg_temp_2, pg_temp_3, etc).
>
> Still no luck, changed the query to:
>
>   select relname, age(relfrozenxid) from pg_class join pg_namespace n on (n.oid = relnamespace) where nspname ~
'^pg_temp'
>
> and no temp tables showed in any database :-(. Any other idea?.

None :-(  Is there any table with a large age value, regardless of
temp-ness?  Does the age of the oldest table correspond to the age of
pg_database.datfrozenxid?  The interesting database is the one with the
largest age(pg_database.datfrozenxid).

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-general by date:

Previous
From: Manuel Sugawara
Date:
Subject: Re: Cannot use a standalone backend to VACUUM in "postgres""
Next
From: Alvaro Herrera
Date:
Subject: Re: Cannot use a standalone backend to VACUUM in "postgres""