Re: Reporting from Standby

Поиск
Список
Период
Сортировка
От Mahesh Shetty
Тема Re: Reporting from Standby
Дата
Msg-id CAJPiW+hqw847AZH4KHF6kip1FU-y1rGficU7oQFuZxMW3h5ZyQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Reporting from Standby  (Don Seiler <don@seiler.us>)
Список pgsql-admin
Based on the output conflicts are mainly caused by Autovacuum & Hot Updates. 

Are these Cancellation for specific sql ?

Regards,
Mahesh Shetty
DbaUniversity.com

On Fri, Dec 2, 2022, 1:10 AM Don Seiler <don@seiler.us> wrote:
On Thu, Dec 1, 2022 at 1:31 PM Mahesh Shetty <maheshetty20@gmail.com> wrote:
What is the replication conflict you are facing - Can you share output from  pg_stat_database_conflicts ?

The errors stopped a few hours ago so I'm not sure if this info is meaningful or not, but here it is. The "foo" database (real name changed) is obviously the app database where all the querying takes place. 

postgres=# select * from pg_stat_database_conflicts;
 datid |  datname  | confl_tablespace | confl_lock | confl_snapshot | confl_bufferpin | confl_deadlock
-------+-----------+------------------+------------+----------------+-----------------+----------------
 17156 | postgres  |                0 |          0 |              0 |               0 |              0
 13399 | template0 |                0 |          0 |              0 |               0 |              0
 16400 | template1 |                0 |          0 |              0 |               0 |              0
 16401 | foo       |                0 |          0 |           6736 |              35 |              0
(4 rows) 

--
Don Seiler
www.seiler.us

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

Предыдущее
От: Don Seiler
Дата:
Сообщение: Re: Reporting from Standby
Следующее
От: jagjit singh
Дата:
Сообщение: LDP over Postgres