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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>, pgsql-general(at)postgresql(dot)org
Subject: Re: Cannot use a standalone backend to VACUUM in "postgres""
Date: 2008-04-08 21:26:57
Message-ID: 8443.1207690017@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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). 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-04-08 21:33:10 Re: More SSL crash woes
Previous Message imageguy 2008-04-08 21:17:57 Re: Number or parameters for functions - limited to 32 ?