Alvaro Herrera writes:
> Temp schemas are not destroyed on session shutdown; they are rather
> destroyed the next time the backend ID is reused. Normally that's not a
> problem, because a backend ID is reused pretty soon. It's only a
> problem when you use so high a backend ID due to high load,
hat either.
Walter
-Original Message-
From: Alvaro Herrera [mailto:alvhe...@commandprompt.com]
Sent: Wednesday, February 03, 2010 3:36 PM
To: Walter Coole
Cc: Merlin Moncure; Grzegorz Jaśkiewicz; Anirban Pal;
pgsql-nov...@postgresql.org; pgsql-general@postgresql.org
Subject: Re: [GE
Walter Coole escribió:
> This didn't seem quite thorough enough, as I found that when a process
> would end (MAX(backendid) went down), the corresponding pg*_temp_
> schema would not go away. I think these were schemas created by a
> previous backend, so would not be cleaned up by a backend that
Walter Coole writes:
> I've gotten a lot of similar schemas, like:
> CREATE SCHEMA pg_toast_temp_1
> AUTHORIZATION postgres;
These schemas are automatically created to hold temporary tables. There
is not a lot of point in removing them, because they'll just reappear
next time you have a lot of
Walter Coole escribió:
> I would like to drop them, since there are so many of them, they make
> it tedious to look through my databases in pgAdmin. Is there a
> reliable way to distinguish between temp schemas that exist because
> they are supposed to be there and those that are not?
Run pg_get
I've gotten a lot of similar schemas, like:
CREATE SCHEMA pg_toast_temp_1
AUTHORIZATION postgres;
and
CREATE SCHEMA pg_temp_1
AUTHORIZATION postgres;
I don't see anything of substance inside those schemas, like tables or
sequences, so I THINK they are the legacy of some previous problem (O
2009/6/8 Grzegorz Jaśkiewicz :
> On Mon, Jun 8, 2009 at 6:57 AM, Anirban Pal wrote:
>> Dear all,
>>
>> Our software use postgres as backend database. It works fine, strange thing
>> is that, it creates so many temporary schemas under schema tab, names like
>> pg_toast, pg_toast_temp_1 like this upt
On 08/06/09 13:57, Anirban Pal wrote:
Dear all,
Our software use postgres as backend database. It works fine, strange
thing is that, it creates so many temporary schemas under schema tab,
names like pg_toast, pg_toast_temp_1 like this upto pg_toast_temp40.
This schemas also reflected in "pg_na
Thank you for your response.
Dear all,
Our software use postgres as backend database. It works fine, strange
thing
is that, it creates so many temporary schemas under schema tab, names like
pg_toast, pg_toast_temp_1 like this upto pg_toast_temp40. This schemas
also
reflected in "pg_names
On Mon, Jun 8, 2009 at 6:57 AM, Anirban Pal wrote:
> Dear all,
>
> Our software use postgres as backend database. It works fine, strange thing
> is that, it creates so many temporary schemas under schema tab, names like
> pg_toast, pg_toast_temp_1 like this upto pg_toast_temp40. This schemas also
>
Dear all,
Our software use postgres as backend database. It works fine, strange thing is
that, it creates so many temporary schemas under schema tab, names like
pg_toast, pg_toast_temp_1 like this upto pg_toast_temp40. This schemas also
reflected in "pg_namespace" table. Can anybody tell me, i
11 matches
Mail list logo
