| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rob Brucks <rob(dot)brucks(at)rackspace(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: NOTIFY command impact |
| Date: | 2017-02-21 23:05:38 |
| Message-ID: | CAKFQuwaynUk3YSvv0kRnE8EPGZrnDCGHfD5rVKC5rzpRgnEEnA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 21, 2017 at 3:47 PM, Rob Brucks <rob(dot)brucks(at)rackspace(dot)com>
wrote:
> If a notify is sent and then PG is immediately shut down, wouldn't PG want
> to save that message for processing after startup?
>
>
>
> Or is the message just discarded?
>
>
>
Adrian gave details but trying to figure out notification semantics across
a system reboot seems like a headache for little benefit.
Its likely assumed that upon first connection the client would eagerly load
the relevant data - capturing the static state of the system at that time -
and then only perform additional queries upon notification.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-02-21 23:11:17 | Re: R: R: Slow queries on very big (and partitioned) table |
| Previous Message | Tom Lane | 2017-02-21 23:03:52 | Re: NOTIFY command impact |