From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Mahmoud Moharam <mmoharam@lucidya.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Materialize view in slave server
Date: Tue, 2 Apr 2019 10:37:50 +1300
Message-ID: <60d328b9-5713-e1a9-f6cf-d33fa9d79ba8@catalyst.net.nz> (raw)
In-Reply-To: <CAEXKJoU2HMR_6J8WD5jhsn32a-TRnP6spc00=v5hL0ec5gbF1Q@mail.gmail.com>
References: <CAEXKJoU2HMR_6J8WD5jhsn32a-TRnP6spc00=v5hL0ec5gbF1Q@mail.gmail.com>
If you use logical replication, you can create the materialized view on
the slave. Which is *better* (master or slave) - depends on whether you
want to have as many reads as possible coming from the slave, and also
details like how much lag (i.e how much out of date) your slave is.
regards
Mark
On 2/04/19 4:02 AM, Mahmoud Moharam wrote:
> Hello All ,
> hope every thing is well with you all ,
> I planned to run stream replication (primary / slave) on my
> environment , and want to make writes on primary and reads from slave
> , so the question is :- I have Materialize view running on primary ,
> what is the best choose to run Materialize view on primary or on slave ?
>
> thanks all
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mark.kirkwood@catalyst.net.nz, mmoharam@lucidya.com, pgsql-admin@lists.postgresql.org
Subject: Re: Materialize view in slave server
In-Reply-To: <60d328b9-5713-e1a9-f6cf-d33fa9d79ba8@catalyst.net.nz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox