Re: Schemas: status report, call for developers - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Schemas: status report, call for developers
Date
Msg-id 1020440376.1517.1.camel@taru.tm.ee
Whole thread Raw
In response to Re: Schemas: status report, call for developers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Schemas: status report, call for developers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2002-05-02 at 16:52, Tom Lane wrote:
> Hannu Krosing <hannu@tm.ee> writes:
> > Is "PROC array slot number" something internal to postgres ?
> 
> Yes.
> 
> If we used PID then we'd eventually have 64K (or whatever the range of
> PIDs is on your platform) different pg_temp_nnn entries cluttering
> pg_namespace.

Should they not be cleaned up at backend exit even when they are in
range 1..MaxBackends ?

> But we only need MaxBackends different entries at any one
> time.  So the correct nnn value is 1..MaxBackends.  BackendId meets the
> need perfectly.

----------
Hannu




pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: HEADS UP: Win32/OS2/BeOS native ports
Next
From: Tom Lane
Date:
Subject: Re: HEADS UP: Win32/OS2/BeOS native ports