Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s1N2t-00BiMa-Pr for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Apr 2024 09:11:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s1N2r-00G4ls-9M for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Apr 2024 09:11:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s1N2q-00G4l3-Vy for pgsql-hackers@lists.postgresql.org; Mon, 29 Apr 2024 09:11:33 +0000 Received: from mail-yb1-xb2a.google.com ([2607:f8b0:4864:20::b2a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s1N2p-000aA9-Ev for pgsql-hackers@postgresql.org; Mon, 29 Apr 2024 09:11:32 +0000 Received: by mail-yb1-xb2a.google.com with SMTP id 3f1490d57ef6-de54b28c3b7so4740361276.1 for ; Mon, 29 Apr 2024 02:11:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714381891; x=1714986691; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DfLsdeym+X+XfcOXY2J8FERzkUUAL6ASg9hX8sjeHJg=; b=Rc1WIBLV1o4Kd+mNFKubScN/HAa6Jmpu+TkPne2yX/oFaVa+cVe1DeT6gWaXaiY5NU I1op+/J2ZL7VHecFlr08GnT4vrQiLf4FgAU4T2QByaZF20JG3noQpl33OT+WYE3VHsRK 335yoHCWgnthxsPuL2K+rvntlo5xeDjpRhIrMgk5rOwczMqfdkIkEjDPsvFHBy9oe6ZD 0pv0wdaEKr292eTA4id3rEdTHAghJ3fuDbk1uC1nuTNdjoMiDW2Jw/n0UJvFeqI+omi8 F/uLyuWRlAlIHWktb1q5abSOXrAxKbZUifPDF85wFhldPUWB6TvV3D4XtcI2CVJkNM/y qTYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714381891; x=1714986691; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DfLsdeym+X+XfcOXY2J8FERzkUUAL6ASg9hX8sjeHJg=; b=baUH7yWa4SBfV+Wivo557idwELxygKmRiqe+WZYW1W5NF8LFxdveHZrIiBi2GoNrbe lrug/tN+8tob9IYtIS2m6gZE1uplhn6epU74ghZm8MJ8jJ5qvFMqPGNAE1k0eB87Hq7V drWFTdhcI53QNdFaiMVSdwxz7Z/lNIerBKsbKhBF+tdqHpBft7nG7fH7L1uNSmMYam0I qBrbjWp02FV318L52yDNxBRosvG9bmqpsufx78UJ2d3syGPzI2jU49e9/Ex2CzaduCMZ oWQTYHqYm0B1BHmyhfznfs7Knjip4RGyqbdadFyY54aL4goi1SgbwTx9ZGBDiP67wfD9 AMOQ== X-Forwarded-Encrypted: i=1; AJvYcCWt9vHyPs0i+vsSLHSi+3nJr5OylldM/o6cfY3NNE5VmPwk3ZaKzzkeKqkdUvkZmW4Oa3r4G/z+guwxOKrsGAQ+VDKKckQBQPIayWAE X-Gm-Message-State: AOJu0Yyvn4JTnb7nnrq0am+ccpyhwh3XofjcxcKDTpH7a17wv/GH/tcx 6idCTrueurxVoQtSu7s1BaQ0aQjWJW58366nKCVkX5QBszY/y1tAgUNuTwQcago0BgXW2HTtg/t dXT62w1Rpm8/YcammxYR+Yd73ZAM= X-Google-Smtp-Source: AGHT+IEz2juUdC9a9jlsX/ZevbQi26dHXSLuxlZzL5pezT/L23+8YTdHzB2dBJDPLpJ5ruRxyrpBuzumVqXrsb4zvuQ= X-Received: by 2002:a25:5f4f:0:b0:de5:965d:7965 with SMTP id h15-20020a255f4f000000b00de5965d7965mr9035005ybm.64.1714381890785; Mon, 29 Apr 2024 02:11:30 -0700 (PDT) MIME-Version: 1.0 References: <1068977.1714367460@sss.pgh.pa.us> <1076837.1714368760@sss.pgh.pa.us> In-Reply-To: From: Richard Guo Date: Mon, 29 Apr 2024 17:11:19 +0800 Message-ID: Subject: Re: A failure in prepared_xacts test To: Michael Paquier Cc: Tom Lane , PostgreSQL-development Content-Type: multipart/alternative; boundary="0000000000009c1c5a061738a329" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009c1c5a061738a329 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Apr 29, 2024 at 2:58=E2=80=AFPM Michael Paquier wrote: > On Mon, Apr 29, 2024 at 01:32:40AM -0400, Tom Lane wrote: > > (BTW, on the same logic, should ecpg's twophase.pgc be using a > > prepared-transaction name that's less generic than "gxid"?) > > I've hesitated a few seconds about that before sending my patch, but > refrained because this stuff does not care about the contents of > pg_prepared_xacts. I'd be OK to use something like an "ecpg_regress" > or something similar there. I noticed that some TAP tests from recovery and subscription would select the count from pg_prepared_xacts. I wonder if these tests would be affected if there are any prepared transactions on the backend. Thanks Richard --0000000000009c1c5a061738a329 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Mon, Apr 29, 2024 at 2:58=E2=80=AFPM M= ichael Paquier <michael@paquier.x= yz> wrote: