| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Mitar <mmitar(at)gmail(dot)com>, 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 16:01:23 |
| Message-ID: | 24cae5b1-fbc6-0cb4-e10c-6cd316dff2f5@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/20/18 7:54 AM, Mitar wrote:
> 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.
>>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kumar, Virendra | 2018-12-20 16:05:16 | Multiple LDAP Servers for ldap Authentication |
| Previous Message | Mitar | 2018-12-20 15:54:02 | Re: Watching for view changes |