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 1020351642.32039.106.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 15:48, Tom Lane wrote:
> Hannu Krosing <hannu@tm.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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] Re : Solaris Performance - 64 bit puzzle
Next
From: Tom Lane
Date:
Subject: Re: Search from newer tuples first, vs older tuples first?