Postgres takes more than 6 minutes to come up during host/standby switch over

Поиск
Список
Период
Сортировка
От RideNext
Тема Postgres takes more than 6 minutes to come up during host/standby switch over
Дата
Msg-id 00ad01d5a5b8$83731320$8a593960$@ridenext.co.in
обсуждение исходный текст
Список pgsql-bugs

Hello!

 

We are using postgres version 9.2.4

 

Our system works in hot/standby mode. There were multiple table with multiple entries in the postgres sql database. During high load transaction, when hot/standby switchover happened. At times it took more than 6 minutes to come up in the standby.

 

Can anyone help to understand the reason why postgres took so much time. Is there anyway to optimise the switchover.

 

If required we can share Postgres logs!

 

Here is the sample logs:

Admin2:

 

postgresql-2019-11-14_000000.log:2019-11-14 01:55:48.456 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_015724.log:2019-11-14 01:57:24.703 GMT LOG:  streaming replication successfully connected to primary

00:02:36:247

 

postgresql-2019-11-14_024053.log:2019-11-14 04:54:03.771 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_050023.log:2019-11-14 05:00:23.346 GMT LOG:  streaming replication successfully connected to primary

00:06:19:575

postgresql-2019-11-14_050023.log:2019-11-14 05:16:41.574 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_052300.log:2019-11-14 05:23:00.681 GMT LOG:  streaming replication successfully connected to primary

00:06:19:107

postgresql-2019-11-14_052300.log:2019-11-14 05:39:10.682 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_054529.log:2019-11-14 05:45:29.030 GMT LOG:  streaming replication successfully connected to primary

00:06:18:348

postgresql-2019-11-14_054529.log:2019-11-14 06:01:37.178 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_060752.log:2019-11-14 06:07:52.763 GMT LOG:  streaming replication successfully connected to primary

00:06:15:585

 

postgresql-2019-11-14_060752.log:2019-11-14 06:24:03.038 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_063019.log:2019-11-14 06:30:19.919 GMT LOG:  streaming replication successfully connected to primary

 

00:06:16:881

 

Admin1:

postgresql-2019-11-14_023941.log:2019-11-14 04:44:33.041 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_044917.log:2019-11-14 04:49:17.444 GMT LOG:  streaming replication successfully connected to primary

00:04:33:403

postgresql-2019-11-14_044917.log:2019-11-14 05:05:22.645 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_051142.log:2019-11-14 05:11:42.154 GMT LOG:  streaming replication successfully connected to primary

00:06:19:509

postgresql-2019-11-14_051142.log:2019-11-14 05:27:57.913 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_053415.log:2019-11-14 05:34:15.305 GMT LOG:  streaming replication successfully connected to primary

00:06:18:392

postgresql-2019-11-14_053415.log:2019-11-14 05:50:24.466 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_055654.log:2019-11-14 05:56:54.619 GMT LOG:  streaming replication successfully connected to primary

00:06:30:153

postgresql-2019-11-14_055654.log:2019-11-14 06:12:49.944 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_061919.log:2019-11-14 06:19:19.795 GMT LOG:  streaming replication successfully connected to primary

00:06:30:851

postgresql-2019-11-14_061919.log:2019-11-14 06:35:15.341 GMT FATAL:  terminating connection due to administrator command

postgresql-2019-11-14_064133.log:2019-11-14 06:41:33.872 GMT LOG:  streaming replication successfully connected to primary

00:06:18:531

 

 

Thanks!

 

В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causes an error
Следующее
От: Konstantin Knizhnik
Дата:
Сообщение: Numeric is not leakproof