Another streaming replication question - Mailing list pgsql-admin

From Mark Steben
Subject Another streaming replication question
Date
Msg-id CADyzmyys52hHwdYXAx3FPeTHuPk3V_ewL2bCoOXNfRieeRqPjA@mail.gmail.com
Whole thread Raw
Responses Re: Another streaming replication question  (Johannes Truschnigg <johannes@truschnigg.info>)
Re: Another streaming replication question  (Rui DeSousa <rui@crazybean.net>)
List pgsql-admin
Good morning,

Thank you all for your responses to my questions about streaming/cascading replication.  I have them ironed out and running on three postgres 9.4 sandbox servers. 
My question is not 'how to ' but more 'best practices'.  We currently have hot standby non-streaming replication with one master serving two standbys in parallel. We wish to convert
to streaming replication.  My concern is that the logshipping load can be quite high - up to 40 16MB logs per minute (during off-hours maintenance). In our current hot standby
environment the logs can queue up on the master side during this period - eventually, during times of lower load they do catch up.  So, a couple questions:
   1.  Can streaming replication work in this high-load situation?
   2.  What, if anything, can I do to make it work better?  Perhaps convert to cascade? Master -->standby1 ---> standby2

I have attached the postgres.conf file for our master for reference.

Any insights welcome.   Thank you.



--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  CRM division of Dominion Dealer Solutions 
95D Ashley Ave.
West Springfield, MA 01089

t: 413.327-3045
f: 413.383-9567

www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
 www.drivedominion.com






Attachment

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL 10.5 : Strange pg_wal fill-up, solved with the shutdown checkpoint
Next
From: Johannes Truschnigg
Date:
Subject: Re: Another streaming replication question