| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org,Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>,"Maeldron T(dot)" <maeldron(at)gmail(dot)com>,Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication bandwith per table |
| Date: | 2017-06-20 04:30:12 |
| Message-ID: | 37319C97-69E9-4F35-AADF-B7E37142DA30@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 20. Juni 2017 03:06:05 MESZ schrieb Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>:
>On 6/19/17 20:50, Maeldron T. wrote:
>>
>
>Not easily. You could play around with pg_xlogdump to see what's going
>on in the WAL. But even if you figure it out, there is not much you
>can
>do about it.
>
>Try perhaps logical replication. That would save you the bandwidth for
>updating all the indexes at least. It might work for you.
Not only the traffic for indexes, for Vacuum too.
(and that can be a lot)
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-06-20 04:48:57 | Re: Error with DefineSavepoint:Unexpected state STARTED |
| Previous Message | Computer Study | 2017-06-20 02:12:43 | Re: Error with DefineSavepoint:Unexpected state STARTED |