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-09-30 03:38:50
Message-ID: CAKFQuwZYx8Znji5vZdvg2VsN4mHx2QbH6kxJzbm=k-C6ZHcy2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Li Japin 2020-09-30 03:42:48 Re: Optimize memory allocation code
Previous Message Amit Langote 2020-09-30 03:34:17 Re: problem with RETURNING and update row movement