| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Mahmoud Moharam <mmoharam(at)lucidya(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Materialize view in slave server |
| Date: | 2019-04-01 21:37:50 |
| Message-ID: | 60d328b9-5713-e1a9-f6cf-d33fa9d79ba8@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raj Gandhi | 2019-04-02 02:06:11 | Re: LIMIT OFFSET with DB view vs plain SQL |
| Previous Message | Frank Alberto Rodriguez | 2019-04-01 15:32:03 | Re: Materialize view in slave server |