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 1v5k0P-00BCUc-Um for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Oct 2025 12:07:54 +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 1v5k0N-007llI-Pt for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Oct 2025 12:07:52 +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 1v5k0N-007lkv-Ey for pgsql-hackers@lists.postgresql.org; Mon, 06 Oct 2025 12:07:52 +0000 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v5k0L-000JSm-2X for pgsql-hackers@lists.postgresql.org; Mon, 06 Oct 2025 12:07:51 +0000 Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-46e4f2696bdso59328685e9.0 for ; Mon, 06 Oct 2025 05:07:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1759752469; x=1760357269; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=NCByahqNJ2JZy09WgqPHJjzCAF3CK2epSw4UfFeYiII=; b=fpIo/nI6nD6+9vNhuTHJaaACkd/dqhtSw9H0TjoZRqIxiKZid7UZX0G1LzVAE7BxO+ qe5jjkQcwvvRsJtSxwAdIkaLMtT7qqaDnyk9ss051EN3WF7lpWN7dN2Tww4+1fEqtb+h OeiwAimYwpwbBUoEF0ErBrhB6O9phvmEn/F+wM00y6mUdxOUEKzFN5emOTMGn6OfRWS2 uOGxf/YQJ0KVEOIi+zmoiTdVXieMJqwuY+J2KnjqtUFwBOYc0YcTcY+NlaF1iGHnY3vy blqXx14xsDn9LcAssHI3+Zjx/8Lpbx4+6zykKusx8506oVJA+95WWzDT6qQa4yv6NlPb 0rQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759752469; x=1760357269; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=NCByahqNJ2JZy09WgqPHJjzCAF3CK2epSw4UfFeYiII=; b=XfqLzu4l9M0Ua+ql2C4NPdu7sPqjI5JOmJbt115/G25l2qcTtTnicOiRaavKodLdaf pwgr43z5UXaMUpATbT0qi2QhkbU5QfOYn75IFcWxRNMMtARBQVlTJ9bCIwgzfjO4iFRJ Qqg832YMtOR9OnSjU7f+FUTHrvdL8r2OdOFUPa1slAMMsSy5tHV/viJNgk8hlV3DBbMl ippGHbsYtW1GanFmdrMQlikWyp5QqV3M/IbcOHqc0zNFV13mk9Yx5Bv2pHUNst6CFTBN J8JyMNR9woGwkmUMqOojmBcnVIZjp291lJZBEMGyGZDtebYftbDN7S3Z2XGcnK+b85o2 ik9g== X-Forwarded-Encrypted: i=1; AJvYcCU96Fl0QnK8U6aU40wke/wbZJOS+kbxchTk+J8aD7GACQcPnhMs26cm9Cb34N747qxC1tH5qEmApuaf1rlR@lists.postgresql.org X-Gm-Message-State: AOJu0Ywkuzp8p3NK4RuTkUbZOflZLdLULXgl1bJ09/kCoInMHlww30IN ACLnwFvIB6gMUA7kswpUcBpiPnslePGteT5um5O6SkO2kSynS1B9WEYB7ULwQ0u7z/4= X-Gm-Gg: ASbGnctt9eDY+pXWC40VEKWA/nfBomYpQlO6l3dsIf3f3WvE9P4omrjotK3l09QGMAX GlPIqDusqxIKvGsBV/eKE1OVcNH+rZVHXeQucMOwupDdb6TjDieBeZytRJRopzUlSYWSq+F7/+c mevdG8WUBXHhvrSjb7P+1BTNxvfv8PmjXvXxdfzSzjCG6s5+be33PDRfBQ6yD3/ITXTzafcIjWn SiaNDE552f/80vY/QzOcIotHbpakF1yMnJIkHIk7fNXVQuy9c085JR6bUvCXnZxbZgsyvAghZj5 7seLymfZHA87roch2PsOYYN3MBh0YnljokIeSieJopdF7fwdle7swpcifkktG4O5900pLp604QW Xd1SRWzTb0bClWPJQFnrqdinZ41oZBCPkqet8VbYtav7YsBtwPifkHh3vIzrWX0a+ld4PuR1JQM +9FaNIzLfz1B3P X-Google-Smtp-Source: AGHT+IERMTvJB5hIlf0/ACCVlGK+aEJUM5cjHtF5rGvkpDzOl0yok4b1jqjMc1YcUcj5iX1/6em8qQ== X-Received: by 2002:a05:6000:2507:b0:3f8:8aa7:464d with SMTP id ffacd0b85a97d-425671ab3afmr7644000f8f.42.1759752469030; Mon, 06 Oct 2025 05:07:49 -0700 (PDT) Received: from laurenz.albe-K4N0CV00F97414D ([2001:871:70:69b7:e3b0:3fa9:a445:fe91]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-4255d8a6b5csm20679897f8f.5.2025.10.06.05.07.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Oct 2025 05:07:48 -0700 (PDT) Message-ID: <946a9fd4468f8d72aa7629a51a6349caf35e8a50.camel@cybertec.at> Subject: Re: The ability of postgres to determine loss of files of the main fork From: Laurenz Albe To: Jakub Wartak , Michael Banck Cc: Aleksander Alekseev , pgsql-hackers@lists.postgresql.org, Tom Lane , Frits Hoogland Date: Mon, 06 Oct 2025 14:07:47 +0200 In-Reply-To: References: <013D63E2-5D75-492E-85FF-1D5CC0148C82@gmail.com> <499686.1759250489@sss.pgh.pa.us> <68dcd1f2.df0a0220.3300c0.f7af@mx.google.com> <68dd1b79.170a0220.3c4175.198f@mx.google.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2025-10-06 at 11:19 +0200, Jakub Wartak wrote: > Anyway, I do not know if opening all the files on startup (or just > crash-recovery?) is the proper way I am not sure if you understand the problem at hand: how can you tell that a segment of a relation is missing? You have to know that there should be a file before you can try to open it. Yours, Laurenz Albe