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

From Bruce Momjian
Subject Re: listen/notify argument (old topic revisited)
Date
Msg-id 200207031749.g63HnSf01762@candle.pha.pa.us
Whole thread Raw
In response to Re: listen/notify argument (old topic revisited)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: listen/notify argument (old topic revisited)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> themselves.  (I'd also be inclined to include the hash code in the
> transmitted message, so that readers could more quickly ignore
> uninteresting messages.)

Doesn't seem worth it, and how would the user know their hash;  they
already have a C string for comparison.  Do we have to handle possible
hash collisions?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: listen/notify argument (old topic revisited)
Next
From: Bruce Momjian
Date:
Subject: Re: libpq++ build problems