On 6/19/17 20:50, Maeldron T. wrote:
> Streaming replication generates too much traffic to set it up between
> different regions for financial reasons. The streaming replication would
> cost more than every other hosting expense altogether (including every
> the traffic, even though it’s web and huge amount of emails).
>
> Is there a way to see in the log how much bandwidth is used per table?
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services