From: | hariprasath nallasamy <hariprasathnallasamy(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Materialized View Incremental Refresh right join |
Date: | 2016-09-02 12:16:49 |
Message-ID: | CAGgejVyA2OHeU8XG=1n+DZj+oJmNChGN69BexdHP_Ymq+QBiVA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all
Using logical decoding i set up a plugin to refresh materialized
views incrementally(only the changes that are did after the previous
refresh). I used the approach that oracle uses for fast refresh of
materialized view using log table to record delta changes.
Mostly i covered for single table and for join(left and right) its an
ideal solution but whenever a right join comes to play a role, its hard to
get these delta change. *Any insights so that i get to proceed further..?*
P.S: For left join Foreign key constraint is followed
Example the view joining 3 tables as [T1 left join T2 left join T3]
Foreign key constraints are imposed so that, a key in T1 is deleted only
after the same keys in T2 and T3 are deleted
Happy weekend
-harry
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-09-02 12:16:53 | Re: [PATCH] Transaction traceability - txid_status(bigint) |
Previous Message | Heikki Linnakangas | 2016-09-02 11:59:48 | Re: Re: PROPOSAL: make PostgreSQL sanitizers-friendly (and prevent information disclosure) |