Re: Best way to use trigger to email a report ?

From: David Gauthier <davegauthierpg(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Christophe Pettus <xof(at)thebuild(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Best way to use trigger to email a report ?
Date: 2020-05-08 18:28:48
Message-ID: CAMBRECBHTevs1RPxbvZ56xxJvh=oqVmCygCm5gQzRni_r8Lang@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Got it.

On Fri, May 8, 2020 at 2:05 PM David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Fri, May 8, 2020 at 10:19 AM Christophe Pettus <xof(at)thebuild(dot)com>
> wrote:
>
>> If you don't want to periodically poll the table, you can use NOTIFY
>> within the trigger to wake up a process that is waiting on NOTIFY.
>>
>
> Kinda.
>
> "With the libpq library, the application issues LISTEN as an ordinary SQL
> command, and then must periodically call the function PQnotifies to find
> out whether any notification events have been received.".
>
> IOW, the interface for the client is still a polling interface its just
> that with LISTEN the event is transient and in-memory only (on the server)
> and thus has less overhead.
>
> David J.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tory M Blue 2020-05-08 19:03:53 Re: Odd postgres12 upgrade is changing or munging a password?
Previous Message David G. Johnston 2020-05-08 18:04:51 Re: Best way to use trigger to email a report ?