Re: 291 pg_toast_temp schemas? - Mailing list pgsql-bugs

From Josh Berkus
Subject Re: 291 pg_toast_temp schemas?
Date
Msg-id 4F99CDA5.4020707@agliodbs.com
Whole thread Raw
In response to Re: 291 pg_toast_temp schemas?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 291 pg_toast_temp schemas?  (Jaime Casanova <jaime@2ndquadrant.com>)
Re: 291 pg_toast_temp schemas?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 4/26/12 11:22 AM, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> summary: database has 291 empty pg_toast_temp schemas.
>
> If your max_connections is 300 or more, this isn't surprising in the
> least.

Yes, they are.

>> ... so, apparently we still have an issue with cleaning up pg_toast_temp
>> schema?
>
> If they are empty, no we don't have a problem with cleaning them up.
> The pg_namespace entries are deliberately left there across sessions,
> to avoid useless catalog churn.

Aha, ok.  Should I add a FAQ item about this?

Also, have we discussed maybe hiding these schemas from \dn?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

pgsql-bugs by date:

Previous
From: rikard.pavelic@zg.htnet.hr
Date:
Subject: BUG #6618: incorrect restore for composite columns when order changes
Next
From: Tom Lane
Date:
Subject: Re: BUG #6618: incorrect restore for composite columns when order changes