| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Anto Aravinth <anto(dot)aravinth(dot)cse(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Building a notification system. |
| Date: | 2018-07-15 16:53:45 |
| Message-ID: | CAKFQuwa2gQeTYxBgcMmvdV=76LPL=gZ7xsGJv2qqe5uimbaMwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sunday, July 15, 2018, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Sunday, July 15, 2018, Anto Aravinth <anto(dot)aravinth(dot)cse(at)gmail(dot)com>
> wrote:
>>
>> I'm not sure, how to get started with this. Read about NOTIFY:
>> https://www.postgresql.org/docs/current/static/sql-notify.html
>>
>>
>> Not sure that fits my use case, thanks for your help in this.
>>
>
> It doesn't. You need to record time stamps for the relevant events and
> use them to decide what is new and what is old.
>
Or, to avoid time skew issues, an equivalent protocol using serial
(big)integers (see create sequence)
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anto Aravinth | 2018-07-15 16:58:32 | Re: Building a notification system. |
| Previous Message | David G. Johnston | 2018-07-15 16:39:33 | Re: Building a notification system. |