| From: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
|---|---|
| To: | Michael Stephenson <domehead100(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Strategy for materialisation and centralisation of data |
| Date: | 2020-05-21 21:19:21 |
| Message-ID: | 20200521211921.GA8702@campbell-lange.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 21/05/20, Michael Stephenson (domehead100(at)gmail(dot)com) wrote:
> On Thu, May 21, 2020 at 10:36 AM Rory Campbell-Lange wrote
> > Presently I've been thinking of using triggers or materialized views in
> > each database to materialise data into a "matview" schema which is then
> > shipped via logical replication to an organisation database when
> > required. New columns in the matview schema tables would ensure replica
> > identity uniqueness and allow the data to be safely stored in common
> > tables in the organisation database.
> You might find Materialize interesting:
>
> https://materialize.io/
Hi Michael. Thanks for the pointer. Materialize.io seems cool but we
don't deal with streaming data, or am I missing something?
Cheers
Rory
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Pereira | 2020-05-21 21:31:00 | Re: pg_basebackup + incremental base backups |
| Previous Message | Michael Stephenson | 2020-05-21 21:06:48 | Re: Strategy for materialisation and centralisation of data |