| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Schemas: status report, call for developers |
| Date: | 2002-05-03 15:39:36 |
| Message-ID: | 1020440376.1517.1.camel@taru.tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
On Thu, 2002-05-02 at 16:52, Tom Lane wrote:
> Hannu Krosing <hannu(at)tm(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Earl | 2002-05-03 17:01:30 | Re: PostgreSQL mission statement? |
| Previous Message | Tom Lane | 2002-05-03 15:25:09 | Re: HEADS UP: Win32/OS2/BeOS native ports |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leslie Herps | 2002-05-04 19:18:04 | [ERROR] pgsql_perl5 |
| Previous Message | Tom Lane | 2002-05-03 14:44:34 | Re: Schemas: status report, call for developers |