Re: Unresolved repliaction hang and stop problem.

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Ha Ka <klasahubert(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Lukasz Biegaj <lukasz(dot)biegaj(at)unitygroup(dot)com>, Krzysztof Kois <krzysztof(dot)kois(at)unitygroup(dot)com>
Subject: Re: Unresolved repliaction hang and stop problem.
Date: 2021-06-16 22:28:28
Message-ID: 202106162228.5w7ltvtus3ou@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021-Jun-16, Ha Ka wrote:

> Here is the upload with generated reports: https://easyupload.io/p38izx
> passwd: johS5jeewo

OK, so I downloaded that and this is the interesting entry in the
profile for the broken case:

# Samples: 5K of event 'cpu-clock'
# Event count (approx.): 59989898390
#
# Children Self Command Shared Object Symbol
# ........ ........ ........ ............. ..................................
#
100.00% 0.00% postgres postgres [.] exec_replication_command
|
---exec_replication_command
WalSndLoop
XLogSendLogical
LogicalDecodingProcessRecord
|
--99.51%--ReorderBufferQueueChange
|
|--96.06%--hash_seq_search
|
|--1.78%--ReorderBufferSerializeTXN
| |
| --0.52%--errstart
|
--0.76%--deregister_seq_scan

What this tells me is that ReorderBufferQueueChange is spending a lot of
time doing hash_seq_search, which probably is the one in
ReorderBufferTXNByXid.

I have, as yet, no idea what this means.

--
Álvaro Herrera 39°49'30"S 73°17'W

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2021-06-16 22:55:46 Re: Question about StartLogicalReplication() error path
Previous Message Tomas Vondra 2021-06-16 22:20:50 Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints