From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgsql-hackers-win32] [PATCHES] fork/exec patch |
Date: | 2003-12-16 23:08:25 |
Message-ID: | 1071616105.5397.12.camel@fuji.krosing.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
Neil Conway kirjutas K, 17.12.2003 kell 00:37:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > In normal operation the only thing that should be signalling a
> > backend is the postmaster.
>
> Oh? What about LISTEN/NOTIFY?
IIRC cancelling queries is done by making a connection to a new backend
and then this backend signalls the one needing to have its query
cancelled. Or is the cancelling done by postmaster without starting a
new backend ?
--------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-12-17 00:00:25 | Re: 7.4 include file conflict |
Previous Message | Alvaro Herrera | 2003-12-16 22:42:38 | Re: [GENERAL][ADMIN]data fragmentation |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-12-17 00:12:29 | Re: fork/exec patch |
Previous Message | Steve Tibbett | 2003-12-16 22:39:26 | Thread-safe signals |