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 1v3xCm-0064uj-4h for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Oct 2025 13:49:16 +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 1v3xCj-002oXL-Qj for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Oct 2025 13:49:14 +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 1v3xCi-002oX6-QC for pgsql-hackers@lists.postgresql.org; Wed, 01 Oct 2025 13:49:14 +0000 Received: from fout-a6-smtp.messagingengine.com ([103.168.172.149]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1v3xCg-000sj2-2k for pgsql-hackers@lists.postgresql.org; Wed, 01 Oct 2025 13:49:12 +0000 Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id 4E61EEC029C; Wed, 1 Oct 2025 09:49:10 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-02.internal (MEProxy); Wed, 01 Oct 2025 09:49:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1759326550; x=1759412950; bh=lbWh3ljvSf oVxAEfuxrmVWz9nBbU4qLYZUIxr73hLII=; b=dC3T+BicgK07DrFrC6x3k2DLss mHOA8bN4QJHbmLYHAq7I/VMrBuCXy4/6rX/dPuLvD6UzFTYX19yPOxKGwkx2ZbGg hYu3vDdWofC2xVcU9rQ+oEoUKjTIkrYsy8glnVIzZWe1X5XnBB3VpxsipfrP77+5 YGfoqZ09mYTJ8m3093XlVHsbHrSI3sgaFuUUiXiYM+hB4RuPt9807GTKz4xjHSm4 XVttnOPYvHoaW86JVO5Ldx/FZIeNL1f3LP39Ieez/KR5lItTHNzBCT1b7t4deTzM oBikqIJrQZCl/ArMQiAzH3ZQI1/eqOPvAoRiekNP9XI4W3/NUwe8dbzbsVMg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1759326550; x=1759412950; bh=lbWh3ljvSfoVxAEfuxrmVWz9nBbU4qLYZUI xr73hLII=; b=knCX4nXt4qUbqmgsHNWofnth6bzhsBCU+g6pk6T2dRE1SW0qXyZ jDILlczTHkYklCAicThA8NplR03ZP3Ynd9tSC17IWd+mkicm57tB/yYcOT6LpYah 8BZ80422kEBhmtHJatZVcU7839BsLV7BjPHa1b3345sovr1emkPb3bziqz79iBwz 4v833aE6f+cn6jQ8mAoKZ3t017mSaFFsmBai18k3f/g+OIrVlFIKhm2RvXxvhNee GTfblMh4BRQqQDQr9g+VsDuGx80RCELEs0cUEpiNsU0nefXNOvKatf81CzjmZy60 Aoqav9IyCvfUVkNvUoVCcj0BFQlNkXv4mtA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdekfeeftdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpeffhffvvefukfhfgggtuggjsehttdfstddttddvnecuhfhrohhmpeetnhgurhgvshcu hfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtffrrghtth gvrhhnpeeffffgledvffegtdevlefgtdeggffhvdekgfegteeiveejkeetudelveejhfeu geenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnh gurhgvshesrghnrghrrgiivghlrdguvgdpnhgspghrtghpthhtohepgedpmhhouggvpehs mhhtphhouhhtpdhrtghpthhtoheplhgruhhrvghniidrrghlsggvsegthigsvghrthgvtg drrghtpdhrtghpthhtohepfhhrihhtshdrhhhoohhglhgrnhgusehgmhgrihhlrdgtohhm pdhrtghpthhtohepphhgshhqlhdqhhgrtghkvghrsheslhhishhtshdrphhoshhtghhrvg hsqhhlrdhorhhgpdhrtghpthhtoheprghlvghkshgrnhguvghrsehtihhgvghruggrthgr rdgtohhm X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Oct 2025 09:49:09 -0400 (EDT) Date: Wed, 1 Oct 2025 09:49:10 -0400 From: Andres Freund To: Laurenz Albe Cc: Frits Hoogland , Aleksander Alekseev , pgsql-hackers@lists.postgresql.org Subject: Re: The ability of postgres to determine loss of files of the main fork Message-ID: References: <013D63E2-5D75-492E-85FF-1D5CC0148C82@gmail.com> <45b3a1dd6be28dd409850a5503c029a97ca0754e.camel@cybertec.at> <483AD9AA-39C1-4F4B-B0D6-4CBA0014E877@gmail.com> <083a4d75ab127a603743058bce26e79ba793494e.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <083a4d75ab127a603743058bce26e79ba793494e.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2025-10-01 15:39:04 +0200, Laurenz Albe wrote: > On Wed, 2025-10-01 at 13:58 +0200, Frits Hoogland wrote: > > I am proposing the database to have the ability to detect when it has missing segments. > > Just a random idea: one solution would be if each segment has a flag that indicates > if that is the last segment or not. But that would break the on-disk storage format, > unless there is room left for an extra flag somewhere in the current layout. It'd also make extensions / truncations more complicated. I rather doubt we're going there. Right now relation extension aren't WAL logged. While there might be reasons to change that, I don't think this is enough justification for doing so. Greetings, Andres