Subject: Re: Materialize view in slave server
To: Mahmoud Moharam <mmoharam@lucidya.com>,
 Pgsql-admin <pgsql-admin@lists.postgresql.org>
References: 
 <CAEXKJoU2HMR_6J8WD5jhsn32a-TRnP6spc00=v5hL0ec5gbF1Q@mail.gmail.com>
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Message-ID: <60d328b9-5713-e1a9-f6cf-d33fa9d79ba8@catalyst.net.nz>
Date: Tue, 2 Apr 2019 10:37:50 +1300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: 
 <CAEXKJoU2HMR_6J8WD5jhsn32a-TRnP6spc00=v5hL0ec5gbF1Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk

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