From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Sheduling in SQL |
Date: | 2001-03-15 17:05:17 |
Message-ID: | 3AB0F64D.8010106@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> I've built applications that do roughly this sort of thing in Postgres
> (some of the protocol changes in 6.4 were done to make it easier ;-)).
I may misremember, but IIRC some older protocol (or at least libpq)
returned 0 as backend pid to listening client if it was notified by itself.
Currently it returns the actual pid for any backend. Is this what you
changed?
Anyhow we need some _documented_ way to get backend pid (there is one
actually received and stored with "cookie" for Ctrl-C processing, but
AFAIK it is neither documented as being the backend id nor is there a
function to get at it).
For my own use I created a C function pid() but perhaps there should be
something mainstream for this.
---------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-15 17:11:28 | Re: Sheduling in SQL |
Previous Message | Tom Lane | 2001-03-15 15:47:59 | Re: Performance monitor signal handler |