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 1s1bb5-00DSgP-4a for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Apr 2024 00:43:50 +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 1s1bb2-002vYM-Ax for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Apr 2024 00:43:49 +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 1s1bb2-002vYE-12 for pgsql-hackers@lists.postgresql.org; Tue, 30 Apr 2024 00:43:48 +0000 Received: from mail-yb1-xb2b.google.com ([2607:f8b0:4864:20::b2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s1baz-000grH-5c for pgsql-hackers@postgresql.org; Tue, 30 Apr 2024 00:43:47 +0000 Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-de607ab52f4so863758276.2 for ; Mon, 29 Apr 2024 17:43:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714437824; x=1715042624; 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=jzR2MVzQB2Ce70lrpCN2HQgPnYyQwhuuhxZILxhqtbY=; b=DrNxmLRXS0fj8hpUDtmQOhdMfX6f6peW52jNAg6mVYRQX6a1vwp3egmEt6hwUQ3lGG BOpCibPpkfPe/lWyQC9yMCZ4K34MLuAyyxUdmXRhuN9rSAV1Vrl6fOf+4CZkYJ69RAm6 r12wtGzGJCIRZ0MWV2veO0w6kwHSL4SwliYwYCZHHjJ4ExgIvRoc7FilZlLvBYtuBaxv wcdcMAH6/zf+rP9RR7e7JsSYd+og0VZzn6lkqYicmbJKheWrpE51vg7xX1DmB00sbo9O /uSZ+TWMjv1LRomRi+TNgO2ozJqDgSgTg31Ke+yLpHYDB0tQnAEn2enMkHgv71vI57Ah XDsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714437824; x=1715042624; 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=jzR2MVzQB2Ce70lrpCN2HQgPnYyQwhuuhxZILxhqtbY=; b=ERzP+0OydrLCI38c+Zt7y3PG3b7aXdniKG1SeuaJM/e8CtB7hvOb7e8XtGM3sfQRSE k9q24akZJyYTSgIilyUA5lxzLTACEeBbTKNERcsqIkvUsoC3uwtvRSQ3BTzLN2V8JQMS 0egOk1RH/ugow9zqGsXa+h4mXFbsCVd8IgY5k5eDMzBYP4KfwWNBHCSTS+kA8rA1W9wi 3jEafdevxm9KtTMDuhb3Kc9+j/BKJem4rKtN6rqT6llaumgTZxMSOV8KOmD3mY7L98z2 ulBeW8AT5FjlSnYERxBxIRV0XxUaO6yPF1ML5nbDj0uH4zTjB6cHA6JBKoWF3OzHU1Iz ycAQ== X-Forwarded-Encrypted: i=1; AJvYcCWv2yiKN4GQ4bjyosLntCIH+kh7+7ArudvinqrorGtds/k3Bdrfn7AKG3p8PXkxwQt0oV0HKJGFgEXQm7ai3XR1nrh66M7cJSplWsgh X-Gm-Message-State: AOJu0YzhouNDGi8ZMJHvu4impdaqwkgNwRqzvVfAMgxlKd8Y9QiqcNdB bzZZ1yTbL3NpApyBMYnkr14OuxGcWx77/d6Cu4p8LEhuZ3O12HefEFSlbxuXK1ycA05SFbODoNk efGxDmsY7JdGIK3BkT5Or1Sqd6xE= X-Google-Smtp-Source: AGHT+IGt+aUly8n/atgZ2Qy2YPfG7jHJka/WQlpK8nc4uT5UAx1Kk5USVjYjm5iLkUtxDdB3JN+OLOndHnml+FFdgmI= X-Received: by 2002:a25:938b:0:b0:dcf:ba3f:a6e9 with SMTP id a11-20020a25938b000000b00dcfba3fa6e9mr12095947ybm.42.1714437823944; Mon, 29 Apr 2024 17:43:43 -0700 (PDT) MIME-Version: 1.0 References: <1068977.1714367460@sss.pgh.pa.us> <1076837.1714368760@sss.pgh.pa.us> <1222343.1714398316@sss.pgh.pa.us> In-Reply-To: <1222343.1714398316@sss.pgh.pa.us> From: Richard Guo Date: Tue, 30 Apr 2024 08:43:32 +0800 Message-ID: Subject: Re: A failure in prepared_xacts test To: Tom Lane Cc: Michael Paquier , PostgreSQL-development Content-Type: multipart/alternative; boundary="0000000000007c6284061745a97b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007c6284061745a97b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Apr 29, 2024 at 9:45=E2=80=AFPM Tom Lane wrote: > Richard Guo writes: > > 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. > > TAP tests shouldn't be at risk, because there is no "make > installcheck" equivalent for them. Each TAP test creates its own > database instance (or maybe several), so that instance won't have > anything else going on. Thank you for the explanation. I wasn't aware of this before. Thanks Richard --0000000000007c6284061745a97b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Mon, Apr 29, 2024 at 9:45=E2=80=AFPM T= om Lane <tgl@sss.pgh.pa.us> = wrote:
Richard G= uo <guofengl= inux@gmail.com> writes:
> I noticed that some TAP tests from recovery and subscription would
> select the count from pg_prepared_xacts.=C2=A0 I wonder if these tests= would
> be affected if there are any prepared transactions on the backend.

TAP tests shouldn't be at risk, because there is no "make
installcheck" equivalent for them.=C2=A0 Each TAP test creates its own=
database instance (or maybe several), so that instance won't have
anything else going on.

Thank you for the e= xplanation.=C2=A0 I wasn't aware of this before.

Thanks
Richa= rd
--0000000000007c6284061745a97b--