Skip site navigation (1) Skip section navigation (2)

Re: temp schemas

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: temp schemas
Date: 2008-08-29 13:07:54
Message-ID: 937d27e10808290607s7eb90cbi77398c999632b30a@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Fri, Aug 29, 2008 at 1:40 PM, Roberts, Jon <Jon(dot)Roberts(at)asurion(dot)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

In response to

Responses

pgsql-general by date

Next:From: Roberts, JonDate: 2008-08-29 13:27:25
Subject: Re: temp schemas
Previous:From: ┬┤gnor gplDate: 2008-08-29 12:56:47
Subject: Full Text Search, plus some General Ideas Beforehand

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group