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 20080408193757.GO9062@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""  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
List pgsql-general
Manuel Sugawara wrote:

> In each database executed:
>
>   select relname, age(relfrozenxid) from pg_class where relnamespace = '10406'::oid;
>
> (note that 10406 is the oid of the pg_temp_1 namespace) none of them
> showed temp tables, Is this the correct way?, Any other idea?.

Hmm, nope -- take away the relnamespace check, because there is a
different namespace for each backend (pg_temp_2, pg_temp_3, etc).  And
as far as I've seen, most leftover temp tables are on "high" temp
schemas (i.e. those belonging to backends that are only used when the
load is high).

--
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: Jeff Amiel
Date:
Subject: Re: More SSL crash woes