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 200207031756.g63Huf502610@candle.pha.pa.us
Whole thread Raw
In response to listen/notify argument (old topic revisited)  (Jeff Davis <list-pgsql-hackers@empires.org>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > 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;
> 
> This is not the user's problem; it is the writing backend's
> responsibility to compute and add the hash.  Basically we trade off some
> space to compute the hash code once at the writer not N times at all the
> readers.

Oh, OK.  When you said "transmitted", I thought you meant transmitted to
the client.

--  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: regress/results directory problem
Next
From: Bruce Momjian
Date:
Subject: Re: listen/notify argument (old topic revisited)