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 1v9qnh-009ZJo-Qx for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Oct 2025 20:11:45 +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 1v9qng-00509j-FC for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Oct 2025 20:11:43 +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 1v9qng-00509a-5y for pgsql-hackers@lists.postgresql.org; Fri, 17 Oct 2025 20:11:43 +0000 Received: from mail-io1-xd2d.google.com ([2607:f8b0:4864:20::d2d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v9qnc-002mK1-3D for pgsql-hackers@postgresql.org; Fri, 17 Oct 2025 20:11:42 +0000 Received: by mail-io1-xd2d.google.com with SMTP id ca18e2360f4ac-911afafcc20so99123839f.3 for ; Fri, 17 Oct 2025 13:11:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1760731898; x=1761336698; darn=postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=z1YjTTZXlsbTfOtWh6YVVQxP9GCnSCyxACkMd3oxvFk=; b=RPVyJuXAIvdPAm0l3bCfIvauY/dfxuv7u+kCL+mXcKQZsYJUVph8As9Bhv0i2YqxIw sGTlEZ3izGjiFeQ50JlZrpH+7U+JPaFBjMaPh1Y9sMV84AaedVuCMkDDpLuL72mfqoop fz2PcJxeY9UdcjylIkmcazEUjz5QURMA3Lv3V+vPiEe/S2vM/lWnfyLjbSYAZQ32jmkt Z4v1q8aMPyjjf53Mr8fa9AiHfwpvBbsVwFkrCZTRxrMGqo6rI4lePFOONg53X/E2e3XY Jyq94DCpy5UJk4eI4NM0FdnuQNvNQ4iHtIVywhHZJuL9KuLDxIH1a2SmdqEnh/8m/xIP uwog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760731898; x=1761336698; h=in-reply-to:content-transfer-encoding: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=z1YjTTZXlsbTfOtWh6YVVQxP9GCnSCyxACkMd3oxvFk=; b=t8CdwNkOKF5SDQAM8vc22kxtB9nqf02E8qpALlaVG1je2XzH1fqvfJPUHlggF1x6e/ ylD8obFdFqQcLzIqXzXN0xwkYxXgrqw5BFpkBzI1dHa96l4IgfGduX2X2kUc7tfBJGV5 aXxoY9d/aR/gcp4NNUfufn+gUxp4/t0hh4CfYkjBGQIPza/W+Yk82+7vI5tQrTC7Z3Br X16B9stdnG7BxXW7wTtgkryOxbfo7mG8d29sjMA/bQUGHaKw+swcCdMEtxq1ySTqqX1v TTwbcj8sN0sZZ8hphTmO57UpRbc80Z824hCaofM9N4yxqAqKoSM0yWV+MoOGZNSA5US9 318Q== X-Forwarded-Encrypted: i=1; AJvYcCWiCeM5LvGHYEhnNeOWQBJdasLrwvxTlJfEnFWfE0cksP7JH8y51kpcoJEDeV8bC8gjIvGwREjzuM1fY7ro@postgresql.org X-Gm-Message-State: AOJu0YyaqbcLgEctvDp4sPdHek7P8Snlbeug0yrSk01yXisozKEwIdjt 8cDh9D8QMPlDbyxQagQGZyayPS/U0pr1AvAnqyPIOEaqMz9ipqcFyzZm X-Gm-Gg: ASbGncuaBhOEeABROwo+WqyL7FB+PN+lRxdIuSbPiN5LGnQoMGjv/ZqBs5Ltqi25s3X a/ZuHFZmThYB4OOAzwN9WDuzO54t7gRT0ZF1Dz3bycc5ug6nTXB1Tb5ATzalBgpN8L2labG2wRg nOw75eCl4OyiSU14zHs6THYNMWIkMFGfKBQ4Ejb7HIEjuhxzLvTZc1KDUC6NrSoidqLGKLt+twQ Aaca3ya+28DWS00VLFeb09PI+VXuD2BDvnmhTnpduVSezOzUDhjsIpVQYMVz3lmUNS1mX2/lYGx bBA6z6p4LRSVuclSaNsy9GpaNEayMolNmSmoLkHT/DyNSp7l08W5pBRE6Ulkm/nTzolTJ0wMtwT iAsLJqueWW9oiRHRpXUdy3qXqCLTFLnuz7rNf939UK6ZUc2mkIjb1Rjd8PUFrLg6lYY1Q+DJw8g jvPKSXyrRtT114s/I/ovHQWHUUpQIu0oMqEKF2w1ApdPfWc9RGijoC7pGEkbP5T02JFw== X-Google-Smtp-Source: AGHT+IE419/JL2RUIf4c/ITfg8ESQz21XMhE7lqynGjxo8EoR/OFvaPmQkO3Oq7u+TWAoK8zmquvkQ== X-Received: by 2002:a05:6602:2dc6:b0:93b:ac2b:d63b with SMTP id ca18e2360f4ac-93e7634f25emr782651039f.6.1760731898492; Fri, 17 Oct 2025 13:11:38 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id ca18e2360f4ac-93e866e066csm20427539f.20.2025.10.17.13.11.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Oct 2025 13:11:37 -0700 (PDT) Date: Fri, 17 Oct 2025 15:11:35 -0500 From: Nathan Bossart To: "David E. Wheeler" Cc: Tom Lane , pgsql-hackers@postgresql.org, Andrew Dunstan , Mankirat Singh Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats() Message-ID: References: <1713509.1760721320@sss.pgh.pa.us> <1723302.1760726712@sss.pgh.pa.us> <78B81B37-9F27-4085-92DA-6B50DFC24361@justatheory.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <78B81B37-9F27-4085-92DA-6B50DFC24361@justatheory.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Oct 17, 2025 at 03:52:18PM -0400, David E. Wheeler wrote: > Adding Mankirat, who developed the ABI checker for his GSoC project. Thanks for chiming in. > Is the idea that the ABI checker just has to scan the first non-comment > line that starts with a commit identifier (SHA or tag)? Yes. > Seems totally do-able, though I don’t know what that `(Apple Git-154)` > bit is doing at the end. I think that's just telling you what version of git I used to create the patch file. > I presume it would list the history of changes in reverse chronological > order, yes? Yes, although we could change it to whatever we want. > If there is a tag _AFTER_ the listed SHA, should we prefer that tag as > the baseline? I don't see any need to consider tags at all. We'd initialize this file when creating the new STABLE branch with a baseline commit near a release candidate or the .0, and then we'd just add future baselines as needed. The ABI checks would always use the latest baseline, even if it points to something before the latest release tag. (At least, this is how I'm thinking about it.) -- nathan