Re: Is there a way to be notified on the CREATE TABLE execution? - Mailing list pgsql-general

From Melvin Davidson
Subject Re: Is there a way to be notified on the CREATE TABLE execution?
Date
Msg-id CANu8FixCFfWYYm61+T7gkbf4FntpSUDPOpoVE=VG_L2fUv+rbw@mail.gmail.com
Whole thread Raw
In response to Re: Is there a way to be notified on the CREATE TABLE execution?  (Francisco Olarte <folarte@peoplecall.com>)
List pgsql-general


On Wed, Jun 20, 2018 at 1:28 PM, Francisco Olarte <folarte@peoplecall.com> wrote:
Melvin:

Maybe old eyes, but ...

On Wed, Jun 20, 2018 at 7:03 PM, Melvin Davidson <melvin6925@gmail.com> wrote:
>>Is there a way to be notified on the CREATE TABLE execution?
> Here is sample code that will notify for a CREATE or DROP table:

Doesn't this trigger just log the events? I think it's missing
something like "Notify create_or_drop" somewhere after the logging (
so a listener knows to look at the log table ).

( Normally I would use something like this, listen to a channel, do a
first scan from the saved last tbl_cl_key, and then do another scan
from the last each time listen fires, it seems the difficult work is
done but it misses the notify to signal listeners and avoid having to
rescan on a timer or a similar thing ).

( Maybe I missed the line, it would not be the first time, that's why I ask ).

Francisco Olarte.

> Maybe old eyes, but ...
>I think it's missing
>something like "Notify create_or_drop" somewhere after the logging (
>so a listener knows to look at the log table ).

Uh, I said it was a SAMPLE. It's not that difficult to add RAISE INFO... or NOTIFY...
which, if you look, is commented out with generic information..
Of course, the exact message is left to the creator.

--
Melvin Davidson
Maj. Database & Exploration Specialist

Universe Exploration Command – UXC

Employment by invitation only!

pgsql-general by date:

Previous
From: Jerry Jelinek
Date:
Subject: Re: Can PostgreSQL create new WAL files instead of reusing old ones?
Next
From: "Enrico Thierbach"
Date:
Subject: Trouble matching a nested value in JSONB entries