| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sheduling in SQL |
| Date: | 2001-03-15 17:11:28 |
| Message-ID: | 14243.984676288@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> Tom Lane wrote:
>> (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?
That was one of the smaller items. The bigger problem was that the
backend wouldn't forward you NOTIFY events unless you issued a constant
stream of dummy queries.
> Anyhow we need some _documented_ way to get backend pid
PQbackendPID() seems adequately documented to me ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-15 17:29:52 | Allowing WAL fsync to be done via O_SYNC |
| Previous Message | Hannu Krosing | 2001-03-15 17:05:17 | Re: Sheduling in SQL |