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-02 15:00:42 |
Message-ID: | 1020351642.32039.106.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 15:48, Tom Lane wrote:
> Hannu Krosing <hannu(at)tm(dot)ee> writes:
> > On Thu, 2002-05-02 at 05:33, Tom Lane wrote:
> >> The temp schema is pg_temp_nnn where nnn is your BackendId (PROC array
> >> slot number). AFAIK there isn't any exported way to determine your
> >> BackendId from an SQL query.
>
> > The non-portable way on Linux RH 7.2 :
>
> >> create function getpid() returns int as '/lib/libc.so.6','getpid' language 'C';
>
> But PID is not BackendId.
Are you sure ?
I was assuming that BackendId was the process id of current backend
and that's what getpid() returns.
What is the Backend ID then ?
Is "PROC array slot number" something internal to postgres ?
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2002-05-02 15:32:57 | Re: DROP TABLE hangs because of same table foreign key |
Previous Message | Tom Lane | 2002-05-02 14:54:44 | Re: Schemas: status report, call for developers |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeffrey W. Baker | 2002-05-02 15:43:23 | Re: Schemas: status report, call for developers |
Previous Message | Tom Lane | 2002-05-02 14:54:44 | Re: Schemas: status report, call for developers |