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 1tAs1A-000YNh-JZ for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Nov 2024 14:37:19 +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 1tAs17-0072VP-S7 for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Nov 2024 14:37:18 +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 1tAs17-0072VF-I5 for pgsql-hackers@lists.postgresql.org; Tue, 12 Nov 2024 14:37:18 +0000 Received: from mail-pg1-x532.google.com ([2607:f8b0:4864:20::532]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tAs14-001YFV-Et for pgsql-hackers@lists.postgresql.org; Tue, 12 Nov 2024 14:37:17 +0000 Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-7ede82dbb63so2878932a12.2 for ; Tue, 12 Nov 2024 06:37:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timescale.com; s=google; t=1731422233; x=1732027033; darn=lists.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=8gui3kTwA6X5cv8onWkkbuL9eXTmS4pWwvU9OmU0s6w=; b=DUrtqfMoef/lAPIY/QQUHBGo/jLm+vGPD/y2dS+PzyN97UXQ2UDXHtHs7lzJfnUlt9 OZFNBkkUv2vXnCdS4ySGwU1bZMaiLRjIVpOtC5j4R6yawIYqpI+5Tg9rM7HaX42dOYYS 4Xx01/LDGQKJmR3yC0zDhJm0Yy3Nyes5Fd9WoUOv+vjv9UKUMeINXN5dO75CNo8RkY1r JjwG8adPeWmQjzaj8ZRf1J0sXkOtO+ZwzhXwc9d3vXqpqnId5OULAgvFXJBB3iNUj/z+ udF//KIknYtm6vV/ZmfRFF5bel0EZPYPFtZmxbXftTVt7yLyA1EMOegHi/PQaO8lkEHi RBsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731422233; x=1732027033; 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=8gui3kTwA6X5cv8onWkkbuL9eXTmS4pWwvU9OmU0s6w=; b=Q7HT0fKRAZu5LEOkJaXFnS2VTMTPGV1Fa73to+rNf4qnNnaMAS4VFlUuktQY5d5XLr drqIQWfq3mWGmypOg/fvtA3FyhOc6sdG8oFncUos9ZvtTL7du3k+uNorJCtcI3lPhGow Whksx4zQYZztNWWe5VOe9HvIcdSo0CK7FWouYQ1OfvgkEkcqZvUx0hCrVX6fmp+eEm3k slUZjvXeYtLW8R+cIy/VLTOOWGVBfFKiuAiXZ+cDa+o64TwsdzxRYqZYsSmy2mgMXdRE Fs1abP3gKFyVq312cnaBnVdRLFAc3R0Zlzjfv8pqbJUJASAEf4YAXmfJBre1WmT/PhgV W34Q== X-Gm-Message-State: AOJu0Yy9i43C65nU0LrQO9Ekc3D5OXxbLghbZBDYznPueiRxSQ6gsBci D5L5GzXDT/Jb05aoOoMK5b3LqYnoqS18xP2ywPfTGri2lWmv5Aq9mOshAIEfqybtl04bWOyz2yV E8jkB0Pb9EIPf6Q3v/xTMrRYoqj3D90Flo4+ggha63h19SFp31ew= X-Google-Smtp-Source: AGHT+IFORZwRLFsOTbuMLL1Otessqco61+4BVVRXMdP2/PlZ+2Cy0GV+0VnJ+FBN/QjMZ9BNrREt/+BSbHq4UlIjbjM= X-Received: by 2002:a17:90b:3847:b0:2e2:e136:a931 with SMTP id 98e67ed59e1d1-2e9b16ea3e7mr22454600a91.6.1731422233297; Tue, 12 Nov 2024 06:37:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Aleksander Alekseev Date: Tue, 12 Nov 2024 17:37:02 +0300 Message-ID: Subject: Re: [PATCH] Refactor SLRU to always use long file names To: PostgreSQL Hackers Cc: Michael Paquier Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi again, Just a quick follow-up. > (*) BTW I noticed a mistake in the commented code. The condition > should be `>=`, not `<`, i.e: > > ``` > if(new_cluster.controldata.cat_ver >= SLRU_SEG_FILENAMES_CHANGE_CAT_VER) > return; > ``` The concentration of caffeine in my blood is a bit low right now. I suspect I may need to re-check this statement with a fresh head. Also it occured to me that as a 4th option we could just get rid of this check. Users however will pay the price every time they execute pg_upgrade so I doubt we are going to do this. -- Best regards, Aleksander Alekseev