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 1tC0lL-008jF8-MX for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Nov 2024 18:09:43 +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 1tC0lI-00BG3U-Bt for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Nov 2024 18:09:40 +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 1tC0lI-00BG3M-24 for pgsql-hackers@lists.postgresql.org; Fri, 15 Nov 2024 18:09:40 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tC0lF-0023lb-QU for pgsql-hackers@postgresql.org; Fri, 15 Nov 2024 18:09:39 +0000 Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-71e5a62031aso1661340b3a.1 for ; Fri, 15 Nov 2024 10:09:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731694176; x=1732298976; 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=Rp5DvLjvrdhNVofI/fRFEKSsuL9Gk0pcvrPxYkxYEzk=; b=VRVlyyXWuzNi8T1tfhuqgvUe55XQLIU7R1k996FprtBtP3pG7qRQh6CDYsclTOlvxU 8vSSrdVSGAs1WfItA625Y3fDC/AgAJzF5cBCovKB4mQEckLUsuGUDnksI682inOsG3+W QmJPZKO+QH5pQ1+OT73o5oq+szgeDOwBOEfSkbeopS2FEF0T87gEMsBAuY2vcdW5zmX0 uxE3koUgzgWNoohlimgkWoCEcqvXDRLLKjelfyG7pLSWm8uFaDguSUg71b3atPpdUrG5 sRshvz0l78mTyGe/52JTZSoKZTkr2DxvHpXG+MUehoL6iskZopqWTBMs/WE6GIPeuyK/ bmtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731694176; x=1732298976; 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=Rp5DvLjvrdhNVofI/fRFEKSsuL9Gk0pcvrPxYkxYEzk=; b=BdQLV/P8zt6hfkHsBJ3xHg5OwQtdYP9nw/zkmKi0Vc+OOnWxJ+qy0qNM5DzDlY3JZk VSOBMIk38vUkfpPfCZlp2wiggLi1eaUuCYHJKhtC/dBmjuDuKdZhmqi8euIESxqEdKfC JUTyiI39BBJEJr9IWo8QHNvv/m+CHBq6i+K9ZiuTOO9O5GX/+XHgB0vcPygDI7KNcs++ 5up2gH3OvIpZ0MtAJXxonYwNkejLsdNdJlytxU8bPxXd5q+SwP1LsjaTDoVbWc/SKYpS iLihEV3erSKmn0dQZXrUwoNJMkYvVyAnnHcb4hm0wEHy6aBlboPiLpPjfm4415jXx1i+ zpMw== X-Forwarded-Encrypted: i=1; AJvYcCVwtlchShzH58B6yxkB5rkFo0QjTY1VYyUnmKuEARA70IeXwLbXQxBAM2yjwmlwADEYOHtDeQpfoz0MUuZU@postgresql.org X-Gm-Message-State: AOJu0YyZAHCqkXe9NoGgOIMT+Y8ztaZmxT2LX7BAHt+SLkS3J4VEhDgH KDR8KU7g05dDDDRmeAJnaMuBq8YPAeMo5OvY5Jqdb0vNbzRj2tQUsWrsDaJbOPjEjESMleEyZyY EQsrKUzR7byKu5z9+RryfObuzRaI= X-Google-Smtp-Source: AGHT+IH7S8bSW+gnWIWCBEpEH9ybyjiXzEe+yULxkArw/Cd39yQxZwJgenrNpUN4Z1Eqk+15Cs7vp/cI3bX903+C+xU= X-Received: by 2002:a17:90b:3d87:b0:2e2:d175:5f8d with SMTP id 98e67ed59e1d1-2ea154dfa68mr4717993a91.10.1731694176369; Fri, 15 Nov 2024 10:09:36 -0800 (PST) MIME-Version: 1.0 References: <1976928.1731614974@sss.pgh.pa.us> <202411142033.u6za5a6ylj2k@alvherre.pgsql> <20241114224108.d0.nmisch@google.com> <2443809.1731683394@sss.pgh.pa.us> <20241115175223.68.nmisch@google.com> In-Reply-To: <20241115175223.68.nmisch@google.com> From: Pavan Deolasee Date: Fri, 15 Nov 2024 23:39:24 +0530 Message-ID: Subject: Re: Potential ABI breakage in upcoming minor releases To: Noah Misch Cc: Tom Lane , Aleksander Alekseev , pgsql-hackers , Marco Slot , Alvaro Herrera , Christoph Berg Content-Type: multipart/alternative; boundary="0000000000003e03dd0626f778aa" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003e03dd0626f778aa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Nov 15, 2024 at 11:22=E2=80=AFPM Noah Misch wro= te: > > > > I'm starting to lean to the opinion that we need a re-wrap. > > Perhaps. Even if we do rewrap for some reason, it's not a given that > restoring the old struct size is net beneficial. If we restore the old > struct > size in v16.6, those who rebuild for v16.5 would need to rebuild again. > Hearing about other ResultRelInfo arrays will help clarify that decision. > Looking more carefully at the usage of `ResultRelInfo` in the PGD code, I think we might also be impacted by it. At one place, we loop through the `es_result_relations` array and a size mismatch there will cause problems. Interestingly, in v14 and above, we read from `es_opened_result_relations`, which is a List, so it should be safe. I will try some tests on v13 to see if they result in crashes. But it seems quite likely by reading the code. Thanks, Pavan --0000000000003e03dd0626f778aa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Fri, Nov 15, 2024 at 11:22=E2=80=AFPM = Noah Misch <noah@leadboat.com&g= t; wrote:


> I'm starting to lean to the opinion that we need a re-wrap.

Perhaps.=C2=A0 Even if we do rewrap for some reason, it's not a given t= hat
restoring the old struct size is net beneficial.=C2=A0 If we restore the ol= d struct
size in v16.6, those who rebuild for v16.5 would need to rebuild again.
Hearing about other ResultRelInfo arrays will help clarify that decision.

Looking more carefully at the usage of `= ResultRelInfo` in the PGD code, I think we might also be impacted by it. At= one place, we loop through the `es_result_relations` array and a size mism= atch there will cause problems. Interestingly, in v14 and above, we read fr= om `es_opened_result_relations`, which is a List, so it should be safe. I w= ill try some tests on v13 to see if they result in crashes. But it seems qu= ite likely by reading the code.

Thanks,
= Pavan

=C2=A0
--0000000000003e03dd0626f778aa--