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 1sclAp-00AH03-LO for pgsql-hackers@arkaria.postgresql.org; Sat, 10 Aug 2024 12:26: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 1sclAo-008XBt-9l for pgsql-hackers@arkaria.postgresql.org; Sat, 10 Aug 2024 12:26:18 +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 1sclAn-008XBl-WF for pgsql-hackers@lists.postgresql.org; Sat, 10 Aug 2024 12:26:18 +0000 Received: from mail-lj1-x22b.google.com ([2a00:1450:4864:20::22b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sclAl-0042He-8W for pgsql-hackers@postgresql.org; Sat, 10 Aug 2024 12:26:16 +0000 Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2f189a2a841so28189631fa.3 for ; Sat, 10 Aug 2024 05:26:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723292773; x=1723897573; darn=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=3Ul24jDj1clFwYN5SCw3RyUksbXyVpUgv/CemheNVxw=; b=Z2Ou0J4ediW909hWHZso7voIcWHicuqtfv2Seqzv6jcBxG8CTYuNaqgdEUzZul+S9J KDprt9hbym/nye42KGxAfPr+6zVXv1u7rXE6HIWXv2EtWKJ2ZTIrQgSALlyyHYxWCWkH irlrWMW5bxF9iSwQgpzkD3XGorUlum5HlyHcYCVJKvDutJphlqGTv0fS6upBcnk+5mbD AkTGIk+U5x8nZCmW/WGtSOpDZv7ej40DEx9U+MAP9fAQ0uWQKegZts/kUuCEnjpNc4GS fnb1Rn7nEnOO0mfndM3VNWsyjl5DPTp2K8jGDSc+Gose2e8ozWetLmZh8+j0OZHvGeJQ 40qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723292773; x=1723897573; 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=3Ul24jDj1clFwYN5SCw3RyUksbXyVpUgv/CemheNVxw=; b=CITvqdIM9wGFNCLmJm+Y3fWGXWwx/r62pfkoJDmL6S8XaUkclSayxlRkp2Lf9za5US i2fvPYsNRwyJJwchVwYcVx2ygZ7bMz4sNiK1gUIICXOr7llFgfeBR/Iv9I6U4FV9Rn3Z N0syicRiRlfCmxLy9B4S+5pILncCU1CaNramyC+J44fFaLdn2TLy0kcqn0bd5751M4zp bp2xy5y+ROaUc4VN1xODNvLfWZbT5ax23sGUdU6HRBML5Q1tzwQOXNwKuEaluxP5OSNT zgYF+7/kGHBsMAPt59g1FTVXPDjynKqOMVAxsPiQGMAAGssOFkK1BNAGVgbFYoHunn0z wxcw== X-Gm-Message-State: AOJu0YwF6Ipq9nZB+gWuPr7j91A9VsaUr487ExR6bULvC5mliX5v+KOn ijU6K9b2NpeNIj9TxaAPKg05GYuMHwxvLQ4ZHCXzv1X4KBT1yPAQU6HxMh5Tn7yrcC3uwDpzb2/ MqdYAVaDutps1NF+ChSZg5usTrdKfcJih X-Google-Smtp-Source: AGHT+IGGCqY1t68YZbpt3EqCH16mycRXmABBA0XKo1Yl7POyrhCb9EfOc7OnpV934/iGzFqskCulqAcT7kj1NZPzDcU= X-Received: by 2002:a2e:b8c8:0:b0:2ef:2685:177d with SMTP id 38308e7fff4ca-2f1a6c6a42emr32467121fa.20.1723292772855; Sat, 10 Aug 2024 05:26:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kirill Reshke Date: Sat, 10 Aug 2024 17:26:01 +0500 Message-ID: Subject: Re: Constant Splitting/Refactoring To: David Christensen Cc: PostgreSQL-development , Stephen Frost , peter@eisentraut.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 13 Mar 2024 at 20:42, David Christensen wrote: > > Here is a version 2 of this patch, rebased atop 97d85be365. > > As before, this is a cleanup/prerequisite patch series for the page > features/reserved page size patches[1]. (Said patch series is going > to be updated shortly.) > > This splits each of the 4 constants that care about page size into > Cluster-specific and -Limit variants, the first intended to become a > variable in time, and the second being the maximum value such a > variable may take (largely used for static > allocations). > > Since these patches define these symbols to have the same values they > previously had, there are no changes in functionality. These were > largely mechanical changes, and as such we should perhaps consider > making the same changes to back-branches to make it so context lines > and the like > would be the same, simplifying maintainer's efforts when applying code > in back branches that touch similar areas. > > The script I have to make these changes is simple, and could be run > against the back branches with only the comments surrounding Calc() > pieces needing > to be adjusted once. > > Thanks, > > David > > [1] https://commitfest.postgresql.org/47/3986/ Hi! Your patchset needs a rebase. Are you going to push it forward? Also, It is better to have more informative commit messages in patches. -- Best regards, Kirill Reshke