Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mrdd1-00081Q-Ec for pgsql-admin@arkaria.postgresql.org; Mon, 29 Nov 2021 10:11:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mrdcz-0003wX-U2 for pgsql-admin@arkaria.postgresql.org; Mon, 29 Nov 2021 10:11:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mrdcz-0003vw-Bo for pgsql-admin@lists.postgresql.org; Mon, 29 Nov 2021 10:11:17 +0000 Received: from mailout2.med.uni-muenchen.de ([138.245.1.13] helo=srvproofp3.srv.med.uni-muenchen.de) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mrdco-0002N1-1y for pgsql-admin@lists.postgresql.org; Mon, 29 Nov 2021 10:11:16 +0000 Received: from pps.filterd (srvproofp3.srv.med.uni-muenchen.de [127.0.0.1]) by srvproofp3.srv.med.uni-muenchen.de (8.16.0.43/8.16.0.43) with SMTP id 1ATA5Esg016848; Mon, 29 Nov 2021 11:10:59 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=med.uni-muenchen.de; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=gw1201801; bh=/Vr81OzXrOFQjZlX9gUhlyZssvNphLozhR9ZPpctbpU=; b=EVdWEHxdCMu0OBgtCTA5ZPb1BUss3R67PR1qYDM/VrSNWFHZUhz2UPaUkb6HIXV0TXwT BW3vfnV9NxDJxYdOn5ZiNVdofFOAIuUQwxb3S0h38eJ426xXl4YJ9rWsj5+OLljvXhPv LdqTrejtcWcMVgYTe7EXQSRLFWhF0nT4W8M= Received: from mailout2.med.uni-muenchen.de ([192.168.21.12]) by srvproofp3.srv.med.uni-muenchen.de with ESMTP id 3ck9hdyqqa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Nov 2021 11:10:59 +0100 Received: from MITEXNOT1.helios.med.uni-muenchen.de (unknown [172.17.9.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mitseppm2.srv.med.uni-muenchen.de (Postfix) with ESMTPS; Mon, 29 Nov 2021 11:10:58 +0100 (CET) Received: from MITMB3.helios.med.uni-muenchen.de (172.17.9.91) by MITEXNOT1.helios.med.uni-muenchen.de (172.17.9.101) with Microsoft SMTP Server (TLS) id 15.0.1497.26; Mon, 29 Nov 2021 11:10:58 +0100 Received: from MITMB5.helios.med.uni-muenchen.de (172.17.9.93) by MITMB3.helios.med.uni-muenchen.de (172.17.9.91) with Microsoft SMTP Server (TLS) id 15.0.1497.26; Mon, 29 Nov 2021 11:10:58 +0100 Received: from MITMB5.helios.med.uni-muenchen.de ([fe80::7d96:f7a5:49d8:268e]) by MITMB5.helios.med.uni-muenchen.de ([fe80::7d96:f7a5:49d8:268e%14]) with mapi id 15.00.1497.026; Mon, 29 Nov 2021 11:10:57 +0100 From: "Dischner, Anton" To: 'Tom Lane' , Chris Cawley CC: "pgsql-admin@lists.postgresql.org" Subject: AW: What do you do with a long running rollback Thread-Topic: What do you do with a long running rollback Thread-Index: AQHX4vQhX7qG6UzIYU6aLaplq0a04qwWE/8AgAQ4pVA= Date: Mon, 29 Nov 2021 10:10:57 +0000 Message-ID: References: <1977259621.1023368.1637951601701.ref@mail.yahoo.com> <1977259621.1023368.1637951601701@mail.yahoo.com> <440098.1637952136@sss.pgh.pa.us> In-Reply-To: <440098.1637952136@sss.pgh.pa.us> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.17.13.18] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SM-outgoing: yes X-Proofpoint-ORIG-GUID: g_5XxInXEMaq_6sago8g5dZk5AFOgKDL X-Proofpoint-GUID: g_5XxInXEMaq_6sago8g5dZk5AFOgKDL List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Tom, do you see heavy disk activity? best, A -----Urspr=FCngliche Nachricht----- Von: Tom Lane =20 Gesendet: Freitag, 26. November 2021 19:42 An: Chris Cawley Cc: pgsql-admin@lists.postgresql.org Betreff: Re: What do you do with a long running rollback Chris Cawley writes: > It's been like that for several days already. Really? Rollback is O(1) in Postgres. I could possibly believe that it's blocked on a lock, but even that would b= e a bug, because transaction abort should never try to take any new locks. A perhaps-more-plausible theory is that you've enabled synchronous commit b= ut your replica is failing to ack the transmission of the abort's WAL recor= d. What are you looking at exactly? regards, tom lane