From: | Ivan Voras <ivoras(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Writing on replicas? |
Date: | 2017-09-19 11:40:36 |
Message-ID: | CAF-QHFXYrBUwUhEiFdXpMBSaagobuiu8hPeNaP46rRGNpi4rFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
I have a possibly unusual case, I've asked about it before on this list.
There is a bunch of reporting being done regularly on some large databases,
which interfere with daily operations performance-wise. So one option is to
have hot async replication in place to a secondary server where the reports
could be run and not impact the main server.
The reporting code is *almost* read-only, with the major exception being
that it creates temp tables for intermediate results. The main tables are
not written to, just the temp tables.
Some time ago when I've asked what to do in this situation, the answer was
that maybe a future version could allow this setup to work. So, I'm asking
again: was something changed in 10.0 which would allow it?
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-09-19 11:48:29 | Re: Writing on replicas? |
Previous Message | Jaime Soler | 2017-09-19 08:44:20 | Re: Postgres 9.6 Logical and Fisical replication |