Re: temp schemas - Mailing list pgsql-general

From Dave Page
Subject Re: temp schemas
Date
Msg-id 937d27e10808290607s7eb90cbi77398c999632b30a@mail.gmail.com
Whole thread Raw
In response to Re: temp schemas  ("Roberts, Jon" <Jon.Roberts@asurion.com>)
Responses Re: temp schemas  ("Roberts, Jon" <Jon.Roberts@asurion.com>)
Re: temp schemas  ("Dave Page" <dpage@pgadmin.org>)
List pgsql-general
On Fri, Aug 29, 2008 at 1:40 PM, Roberts, Jon <Jon.Roberts@asurion.com> wrote:

>> Why have you got thousands of them?  If you are running with thousands
>> of active backends, may I suggest a connection pooler?
>>
>
> I don't know.  It looks like a bug to me where a temp table is created
> and dropped on commit but the next time the function executes and
> creates a new temp table, it does this in another temp schema.  It does
> this over and over until I have thousands of temp schemas that aren't
> used.

Is this vanilla PG, or your Greenplum install?

> It looks this SQL is executing when connecting with pgAdmin which
> doesn't exclude temp schemas.  Even though I don't have it configured to
> show temp schemas, the SQL doesn't exclude these records.  This is with
> 1.8.2 of pgAdmin.

Oh, that's weird - that code is filtering out system objects client
side for some reason. I'll look at that.


--
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: MySQL LAST_INSERT_ID() to Postgres
Next
From: "Roberts, Jon"
Date:
Subject: Re: temp schemas