Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncWXa-0007Ym-3h for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Apr 2022 18:07:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ncWXY-0002R0-GN for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Apr 2022 18:07:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncWXX-0002Qr-Rb for pgsql-hackers@lists.postgresql.org; Thu, 07 Apr 2022 18:07:28 +0000 Received: from mail-wr1-x433.google.com ([2a00:1450:4864:20::433]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ncWXR-0004qd-JC for pgsql-hackers@postgresql.org; Thu, 07 Apr 2022 18:07:27 +0000 Received: by mail-wr1-x433.google.com with SMTP id z1so9063430wrg.4 for ; Thu, 07 Apr 2022 11:07:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F5M2b+4ztOqx6xpW9DCN/n+6ZU/13HWrWi8UWJ2Fm2w=; b=JdK5oK1iMu+wrm8NP60qdAjPZwF2Xb44HAti7tBMBQv+xnLNla/RhRnoBVxAKnDIJQ CWO98RBNr2mr3buN+Hxa0ifLwwYuueEtQ6qRpLifJYBk99SRNlsNYv96MlwIpVSN3V1i JSkXU9pD/fnuUb7kzfGiiVHmDVGiuKNms7OlkwvUpMaREcwYoT8Q+Lmh/ZehwldDa8FC v8D69wMCCGkZpyiwPtY9ISB+PZT10oU28QhNu4x4X9RS4GcdN5hmPk1935h2T8ioTDaB ZRsjve2e+ty1CXhXzgWGHW4qim4GeHTYpEmToLnUW9vHpt2YZKPwc0PSaOAi294XxVXE 4cGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F5M2b+4ztOqx6xpW9DCN/n+6ZU/13HWrWi8UWJ2Fm2w=; b=gtMwUyb9cgVU5NINCP/Y0DMLubnDQanr+Z7xJmE5tu4KxVxtOIdwYiYBf78F5IbGwz KysDRntQPB/wNGSw7+we1xCMG8JBK8I+BYIUyhrlTSTUJU/AC6oHqtVbnkSGjz1GGGon xbN7ALUUaZUG4tAcl4aldi17kMIwy4IeKLrvUCb5TLqp7MRG1pKZ+rto38GFWMwmAfEP meWQVAcTHiHgHHIQz4BmZkpCekIpxN2pfZXO+a30Ymhu51kYSGVBjlBG1Fn/9mKMCr34 dOQk1sVWjbiE1O1MaqHv4UsA13L/aopGRbf8h2sWsQhxyKb533zmY4hTExa8Y/yPmiiX mcbA== X-Gm-Message-State: AOAM533azCl12GWBqr8S2MR5JKh/gA74YlmwefcGIZzU77Bh1Dxe/eco 7D3Gc8Fgs8XPrCGY7KcivhYj7gHFNyU0r4iKniZkns6Lnjx7M+2UCXXYAJ8O++7dIPl7x2ARreC ceGdWh4DU3Iz7H3VfqwVuxXzM2vvi59dmoaasr+a4JLn7svtizD7mnDmdpWcn3t8QICvr+aXbLp 1driaHriekMJ0GfikbeWoCEBlczyAPGmW240wM X-Google-Smtp-Source: ABdhPJylIWMVG8i2BwN1Q93wrv85m2pQ3dM5dBm7SbsbFppjmuz5xE4ExuxgJZwaVX13DG4hp9qFMA== X-Received: by 2002:adf:fecf:0:b0:1f0:62e0:bcd8 with SMTP id q15-20020adffecf000000b001f062e0bcd8mr11767138wrs.61.1649354839579; Thu, 07 Apr 2022 11:07:19 -0700 (PDT) Received: from smtpclient.apple (cst2-164-157.cust.vodafone.cz. [31.30.164.157]) by smtp.gmail.com with ESMTPSA id v18-20020adfc5d2000000b0020589b76704sm18355478wrg.70.2022.04.07.11.07.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Apr 2022 11:07:18 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\)) Subject: Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.] From: Petr Jelinek In-Reply-To: Date: Thu, 7 Apr 2022 20:07:17 +0200 Cc: Tom Lane , Markus Wanner , "pgsql-hackers@postgresql.org" , Kyotaro Horiguchi Content-Transfer-Encoding: quoted-printable Message-Id: <051E2C40-14DF-4AE4-9273-A9A42CDAB5C2@enterprisedb.com> References: <2358496.1649168259@sss.pgh.pa.us> To: Robert Haas X-Mailer: Apple Mail (2.3693.40.0.1.81) X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 7. 4. 2022, at 17:19, Robert Haas wrote: >=20 > On Tue, Apr 5, 2022 at 10:17 AM Tom Lane wrote: >> What I think you need to do is: >>=20 >> 1. In the back branches, revert delayChkpt to its previous type and >> semantics. Squeeze a separate delayChkptEnd bool in somewhere >> (you can't change the struct size either ...). >>=20 >> 2. In HEAD, rename the field to something like delayChkptFlags, >> to ensure that any code touching it has to be inspected and updated. >=20 > Here are patches for master and v14 to do things this way. Comments? Yeah I think this should do it (compilers should warn on master even = without the rename, but who notices that right? :) ) Thanks, Petr