| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Igor Korot <ikorot01(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to watch for schema changes |
| Date: | 2018-12-03 18:06:11 |
| Message-ID: | CAKFQuwbNzGjpjizwb+2Z_j4n2tKwb4XB7aR_Na2iREJkMmRg+w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 3, 2018 at 10:59 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> > As I say - I'm trying to make it work from both ODBC and libpq
> > connection (one at a time)
IIUC what is being proposed is:
Once, on the server, the DBA issues:
CREATE EVENT TRIGGER (the function it runs issues NOTIFY
'channel-name' - even if no one is listening at any given point in
time)
Upon connection your client application executes:
LISTEN 'channel-name'
And then handles notification events from the channel normally.
The client itself never issues CREATE EVENT - nor, frankly, should it.
It shouldn't have sufficient permissions to do something like that.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-12-03 18:09:14 | Re: Query never completes with an OR condition |
| Previous Message | Adrian Klaver | 2018-12-03 17:59:22 | Re: How to watch for schema changes |