| From: | Mitar <mmitar(at)gmail(dot)com> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Watching for view changes |
| Date: | 2018-12-20 15:54:02 |
| Message-ID: | CAKLmikMsXV+bAP-Mk7MphwsPhtkKZGJ4iGOQFE8pkMaDcv3uXQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi!
Thanks. Care for a link or at least thread subject?
Also, Googling around this seems a pretty popular request. I am quite
surprised that there is not something out-of-box available for this,
efficient and scalable.
Mitar
On Thu, Dec 20, 2018 at 7:33 AM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>
> On 12/20/18 3:17 AM, Mitar wrote:
> > Hi!
> >
> > I am trying to see how I could use NOTIFY/LISTEN to watch changes of a
> > complicated SELECT query which spans multiple tables. Ideally, I would
> > like to leave to PostgreSQL to determine when some data (and which
> > data) in the result of the SELECT query has changed. So I am thinking
> [snip]
>
> There was a LONG thread on this list a few months ago about monitoring for
> DDL changes. It should prove helpful (or cause you to despair).
>
>
> --
> Angular momentum makes the world go 'round.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-12-20 16:01:23 | Re: Watching for view changes |
| Previous Message | Ron | 2018-12-20 15:33:01 | Re: Watching for view changes |