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 1n9vHG-0004bU-S2 for pgsql-committers@arkaria.postgresql.org; Tue, 18 Jan 2022 20:40:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n9vHF-00006o-71 for pgsql-committers@arkaria.postgresql.org; Tue, 18 Jan 2022 20:40:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9vHD-00006H-Bm for pgsql-committers@lists.postgresql.org; Tue, 18 Jan 2022 20:40:24 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9vH8-0001hC-KP for pgsql-committers@lists.postgresql.org; Tue, 18 Jan 2022 20:40:23 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 970673200EAD; Tue, 18 Jan 2022 15:40:14 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 18 Jan 2022 15:40:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=G7jd14dLBsSmWRo3cmKLZENYzJ5 qhZVKVdepF6Do5po=; b=Aj6OeA82uhfGM0PFiHotDeBI4eROWEX/m+8SW4Bi69p JOxVxJOHviyDzkT2iuvIn2qNuanOUHuUwUiGVv5IDIq+6k236rZOHPBF97Ni+kfs q8Kh1BfT0/W4MvUeCH3tz2NlZHXsHjRka35xnffVopCCF2VMFJw5QvUsWsOIgtTX HPe/lmoZTqGLV7L1fUTXPbtrrLgPnyGYgGalkUvsi2XuOG0PAYl5bkUGnRn+GwjR IugfZBraZAL+yA/FazzgRmusC3wQOsBN/FeYqcIinWEqKvZGWZR6OH4rzTPB0eBn QLYmHBFSYWsij23KwbQPIlW0OZGxbTomaax32nN+SjA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=G7jd14 dLBsSmWRo3cmKLZENYzJ5qhZVKVdepF6Do5po=; b=NTKomz/BbOMFslYjPCJZlV FPAf2KtHoYXJaOzmYgjgaX9yJFuzt0FQcbpIr8Bfd5EvB3qorbm/PgQBTZV85vYj TPTolnBH7AFNTLKhYrNYthQ7b5vStku22JlwWCn1DBztH/p8AkwNK+X8OcporM8D UMSOHdstmFr0ppWKuvy2ZBXDbHFybRpPB4+N1nEjrlrMWzlXpIfwdvyPfVZznL45 xeENFxoceclIOrs6fzpLQQvdr7+gNv3OkHIcgwDEwwDHjGWpBC/PW5PcVC7AN4ej jilk5M4sxNoJZBsucB526PyjpTCzvY6bGOFbnOh9KQ8vrDPuYd4P43evRSDsHkrg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefgddugedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtffrrg htthgvrhhnpeetheehiefgudelhfevvddvtdejheehkeelteekveeggeduieelieduuefg fedtjeenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgr iigvlhdruggv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 18 Jan 2022 15:40:13 -0500 (EST) Date: Tue, 18 Jan 2022 12:40:12 -0800 From: Andres Freund To: Tom Lane Cc: Thomas Munro , Michael Paquier , Thomas Munro , pgsql-committers Subject: Re: pgsql: Test replay of regression tests, attempt II. Message-ID: <20220118204012.qpfas4fmvc55g4ei@alap3.anarazel.de> References: <20220117203746.oj43254j5jurbneu@alap3.anarazel.de> <374643.1642536944@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <374643.1642536944@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-01-18 15:15:44 -0500, Tom Lane wrote: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2022-01-18%2019%3A50%3A57 > > That reloptions test has been there awhile, and we weren't seeing > issues with it before. What about the replication environment > would cause VACUUM to behave differently? Maybe it thinks there > are non-removable tuples because the walsender is holding back > global xmin? hot_standby_feedback isn't enabled, so it shouldn't... I wonder if it's just a question of the different configuration used by Cluster.pm, rather than the fact that a replica is actually connected. Locally I see the following additions to the configuration for the primary in 027_stream_regres.pl fsync = off restart_after_crash = off log_line_prefix = '%m [%p] %q%a ' log_statement = all log_replication_commands = on wal_retrieve_retry_interval = '500ms' stats_temp_directory = 'pg_stat_tmp' wal_level = replica max_wal_senders = 10 max_replication_slots = 10 wal_log_hints = on hot_standby = on shared_buffers = 1MB max_connections 25 max_wal_size = 128MB port = 63698 unix_socket_directories = '/tmp/098ygO1bAF' listen_addresses = '' max_prepared_transactions = 10 That's an extremely small shared_buffers for running the regression tests, it'd not be surprising if that provoked problems we don't otherwise see. Perhaps VACUUM ends up skipping over a page because of page contention? Also, it's odd that there's "max_connections 25" without an equal sign. I'd kind of expected that to cause an error.... Greetings, Andres Freund