Re: listen/notify argument (old topic revisited) - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: listen/notify argument (old topic revisited)
Date
Msg-id GNELIHDDFBOCMGBFGEFOGEOKCCAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: listen/notify argument (old topic revisited)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: listen/notify argument (old topic revisited)  (Hannu Krosing <hannu@tm.ee>)
Re: listen/notify argument (old topic revisited)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Of course, a shared memory system probably is going to either do it
> sequentailly or have its own index issues, so I don't see a huge
> advantage to going to shared memory, and I do see extra code and a queue
> limit.

Is a shared memory implementation going to play silly buggers with the Win32
port?

Chris





pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: Integrating libpqxx
Next
From: "Christopher Kings-Lynne"
Date:
Subject: libpq++ build problems