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 1u6cbm-001wfI-VQ for pgsql-hackers@arkaria.postgresql.org; Sun, 20 Apr 2025 21:53:51 +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 1u6cbj-00FovX-Ad for pgsql-hackers@arkaria.postgresql.org; Sun, 20 Apr 2025 21:53:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u6cbi-00FovO-Lh for pgsql-hackers@lists.postgresql.org; Sun, 20 Apr 2025 21:53:47 +0000 Received: from mail-pl1-x631.google.com ([2607:f8b0:4864:20::631]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u6cbf-0017kA-0d for pgsql-hackers@postgresql.org; Sun, 20 Apr 2025 21:53:46 +0000 Received: by mail-pl1-x631.google.com with SMTP id d9443c01a7336-2255003f4c6so38705205ad.0 for ; Sun, 20 Apr 2025 14:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1745186022; x=1745790822; darn=postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=dHNH499Tqgi8ONGtrbKBS532dYrYH580Bq7XVC+KasU=; b=T8eRQWyhkOflX20JQSWT53lnFT18ArWXoH9KxBbIFaYAD1EJEtoHFZKgHJSm2AlNVO K9YxJxGEDukISnAND3N1KqVD3EBssfCLveVOrhNJLpTOKHwlTSLqbBBD1fWlT0gvXF8G LLRb8uJNfUnYDDNznnh1QY2Wm+RP6i/Kmr9ro= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745186022; x=1745790822; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=dHNH499Tqgi8ONGtrbKBS532dYrYH580Bq7XVC+KasU=; b=iB22Oq3I/I7Cd2N5WalCdB3nxRDTNI1hllQPXT3ZS7HvKQ4kSaW8jwxORX6+RVqAER 70AZ7aEKtRGabU0xkFBkuCbmjoYrzVuIYAd44Y1LlUjc9Fd9KT6pzkeaoddasQnQpATs eOqI8kESxJXkogDRPmnuaU/T2mUN2B4GDHFKTbG7E9GajI7bK4A3pQ3iWCXWiYJIheiE HWUrxNb3ZX98WbhSDzuEUM9PBg1EVhXAyFOuHfCh7FqFIZfW2aFvWpgF3ZUX6Pw8fcLm N5MmM/L4Sjcglksqme+kyDdyDHNU8U1gWX98dq8gw4q3a2nCb5m75/v2pg7HvYAKqCoU EJ8A== X-Forwarded-Encrypted: i=1; AJvYcCUQoaIMSta9eewBDpOJB+Ajf+1A2qv+zqfxx6unPX9pOr1BVM/DpSvYLT5TNx0nF4QtUMrqkezOhFSkG4F8@postgresql.org X-Gm-Message-State: AOJu0YyTi4ttDz60S4mzygASGbC7gGaONfTCln2VBfX6uwWS+3LbTxwa V+EPN1vfAzm/oeYBXiXnyBu52uSgIptqBxvJImR7qIJdejGFYl+vHurlmIXqhg== X-Gm-Gg: ASbGncuzqStWUA1CyKIdIBvuc3l9kmSzue2MdtKXWC//fcFjt6qeq7kYIVxDNaNgJvg y3ViRtifurVTynvlZ1DferEHN2pC0Jtj80sXdEJM+cvebHm83RL+B5Cgo/79HmFCDIMlrDZzTL5 RdBLtiDHhoG00FCjkfC/EI2frM4YbJFXPcTVuA5dTj7lP8273UcVmkm5iuVbL/HPy0xhakzDAOj 4+yu0ru5lHDJLPSlyuHaC+chBOrX92ghfWQWKCzVmShZFou3AQz75qVFDrLpQ3L+POKp1lvtJi4 8hknmF1njWmhuOTlFWsNhGfqsfxbKNwCc4lhhA== X-Google-Smtp-Source: AGHT+IFmIdXXLtSzCv+3jPx1/HH2v5MQWzIo1w5FkoOsGqzREL4/leI4l3vRYnmvNzy4RLq5Kns3UQ== X-Received: by 2002:a17:903:1aa6:b0:224:2201:84da with SMTP id d9443c01a7336-22c5356de05mr123402495ad.6.1745186021758; Sun, 20 Apr 2025 14:53:41 -0700 (PDT) Received: from google.com ([2601:647:5600:80d0::31cd]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-73dbfaac278sm5138753b3a.128.2025.04.20.14.53.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 Apr 2025 14:53:41 -0700 (PDT) Date: Sun, 20 Apr 2025 14:53:39 -0700 From: Noah Misch To: Andres Freund Cc: Tom Lane , Nathan Bossart , Michael Paquier , Robert Pang , Kyotaro Horiguchi , robertmhaas@gmail.com, pgsql-hackers@postgresql.org Subject: Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Message-ID: <20250420215339.e8.nmisch@google.com> References: <20250312012315.fd.nmisch@google.com> <20250403002900.5d.nmisch@google.com> <2461391.1743865633@sss.pgh.pa.us> <20250405191339.8d.nmisch@google.com> <20250406020958.95.nmisch@google.com> <20250413153312.12.nmisch@google.com> <850092.1744559517@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Apr 14, 2025 at 09:19:35AM +0900, Michael Paquier wrote: > On Sun, Apr 13, 2025 at 11:51:57AM -0400, Tom Lane wrote: > > Noah Misch writes: > > > Tom and Michael, do you still object to the test addition, or not? If there > > > are no new or renewed objections by 2025-04-20, I'll proceed to add the test. Pushed as commit 714bd9e. The failure so far is https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-20%2015%3A36%3A35 with these highlights: pg_ctl: server does not shut down 2025-04-20 17:27:35.735 UTC [1576688][postmaster][:0] LOG: received immediate shutdown request 2025-04-20 17:27:35.969 UTC [1577386][archiver][:0] FATAL: archive command was terminated by signal 3: Quit 2025-04-20 17:27:35.969 UTC [1577386][archiver][:0] DETAIL: The failed archive command was: cp "pg_wal/00000001000000000000006D" "/home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/recovery/045_archive_restartpoint/data/t_045_archive_restartpoint_primary_data/archives/00000001000000000000006D" The checkpoints and WAL creation took 30s, but archiving was only 20% done (based on file name 00000001000000000000006D) at the 360s PGCTLTIMEOUT. I can reproduce this if I test with valgrind --trace-children=yes. With my normal valgrind settings, the whole test file takes only 18s. I recommend one of these changes to skink: - Add --trace-children-skip='/bin/*,/usr/bin/*' so valgrind doesn't instrument "sh" and "cp" commands. - Remove --trace-children=yes Andres, what do you think about making one of those skink configuration changes? Alternatively, I could make the test poll until archiving catches up. However, that would take skink about 30min, and I expect little value from 30min of valgrind instrumenting the "cp" command.