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

From Tom Lane
Subject Re: Cannot use a standalone backend to VACUUM in "postgres""
Date
Msg-id 8443.1207690017@sss.pgh.pa.us
Whole thread Raw
In response to Re: Cannot use a standalone backend to VACUUM in "postgres""  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
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).  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).

Yeah, because the low-numbered ones get recycled first.  To have a temp
table survive for long enough to create this problem, it's pretty much
got to be in a high-numbered temp schema.

            regards, tom lane

pgsql-general by date:

Previous
From: imageguy
Date:
Subject: Re: Number or parameters for functions - limited to 32 ?
Next
From: Tom Lane
Date:
Subject: Re: More SSL crash woes