Re: Listen / Notify rewrite

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Andrew Chernow <ac(at)esilo(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-hackers(at)postgresql(dot)org, Andrew Chernow <andrew(at)esilo(dot)com>
Subject: Re: Listen / Notify rewrite
Date: 2009-11-13 15:13:45
Message-ID: b42b73150911130713k23392553m6b4b17e64280693a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 13, 2009 at 10:00 AM, Andrew Chernow <ac(at)esilo(dot)com> wrote:
> I think the original OP was close.  The structure can still be fixed length
> but maybe we can bump it to 8k (BLCKSZ)?

The problem with this (which I basically agree with) is that this will
greatly increase the size of the queue for all participants of this
feature if they use the payload or not. I think it boils down to
this: is there a reasonably effective way of making the payload
variable length (now or in the future)? If not, let's compromise and
maybe go with a larger size, maybe 256 or 512 bytes.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aidan Van Dyk 2009-11-13 15:14:02 Re: next CommitFest
Previous Message Robert Haas 2009-11-13 15:12:55 Re: next CommitFest