From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: 291 pg_toast_temp schemas? |
Date: | 2012-04-26 22:35:17 |
Message-ID: | 4F99CDA5.4020707@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 4/26/12 11:22 AM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-04-26 22:39:01 | Re: BUG #6618: incorrect restore for composite columns when order changes |
Previous Message | rikard.pavelic | 2012-04-26 22:20:51 | BUG #6618: incorrect restore for composite columns when order changes |