Re: NOTIFY docs fixup - emit and deliver consistency

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: NOTIFY docs fixup - emit and deliver consistency
Date: 2020-10-01 23:39:00
Message-ID: CAKFQuwZx0eYNO-rzy4_YXpkcsm02sqtN_sGvWqyASaUFYhecMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 29, 2020 at 8:38 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Tue, Sep 29, 2020 at 7:58 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Maybe we could use terminology along the lines of "added to the
>> queue" and "removed from the queue"?
>>
>
> Quickly looking it over with this in mind there are a few spots that can
> be cleaned up and linked together by explicitly talking about a FIFO queue
> as the mechanism instead of the less precise send/process/deliver. A bit
> more invasive but I think it will be done more clearly with this approach.
>

As attached.

Attachment Content-Type Size
v2-doc-notify-queue-focus.patch application/octet-stream 8.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2020-10-02 00:00:53 Re: Asynchronous Append on postgres_fdw nodes.
Previous Message Michael Paquier 2020-10-01 23:36:57 Re: Rejecting redundant options in Create Collation