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

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

Manuel Sugawara wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2008-04-08 22:25:27 Re: Cannot use a standalone backend to VACUUM in "postgres""
Previous Message Jeff Amiel 2008-04-08 22:08:09 Re: More SSL crash woes