MIME-Version: 1.0
References: <20260415105718.tomuncfbmlt67oel@poseidon.home.virt> <CAFC+b6q4pF=BSdfOaagRcW74Nmnyz1UMgPcNKRJMFrAe7K3gHQ@mail.gmail.com>
In-Reply-To: <CAFC+b6q4pF=BSdfOaagRcW74Nmnyz1UMgPcNKRJMFrAe7K3gHQ@mail.gmail.com>
From: Ayush Tiwari <ayushtiwari.slg01@gmail.com>
Date: Wed, 22 Apr 2026 17:28:41 +0530
Message-ID: <CAJTYsWX5jTfC41mN7G8o05NRQdkpML-MJSB8kx3TM_u44pPb7Q@mail.gmail.com>
Subject: Re: Bug in CREATE TABLE .. LIKE .. INCLUDING STATISTICS?
To: Srinath Reddy Sadipiralla <srinath2133@gmail.com>
Cc: Julien Tachoires <julien@tachoires.me>, dgrowleyml@gmail.com, 
	pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000007224e206500b412c"
Archived-At: <https://www.postgresql.org/message-id/CAJTYsWX5jTfC41mN7G8o05NRQdkpML-MJSB8kx3TM_u44pPb7Q%40mail.gmail.com>
Precedence: bulk

--0000000000007224e206500b412c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On Thu, 16 Apr 2026 at 13:14, Srinath Reddy Sadipiralla <
srinath2133@gmail.com> wrote:

> Hi Julien,
>
> On Wed, Apr 15, 2026 at 7:47=E2=80=AFPM Julien Tachoires <julien@tachoire=
s.me>
> wrote:
>
>> Hi,
>>
>> One of our customer is experiencing an issue when executing CREATE TABLE
>> .. LIKE .. INCLUDING ALL; on 14, the following kind of error happens:
>> ERROR: cache lookup failed for attribute X of relation ZZZZZZ
>>
>> It seems to come from generateClonedExtStatsStmt(): get_attname()
>> appears to be called with an attribute number (attnum) that does not
>> exist.
>>
>
> yeah, i was able to reproduce and also check the flow which is the same
> as you mentioned.
>

I looked into this and the issue is in generateClonedExtStatsStmt().
It passes the child's relation OID
to get_attname() with attribute numbers from the parent's stxkeys.
With dropped columns the attnums don't match.

Julien's patch fixes that, it likely needs to be backported too.

Regards,
Ayush

--0000000000007224e206500b412c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi,=C2=A0</div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, 16 Apr 2026 at 13:1=
4, Srinath Reddy Sadipiralla &lt;<a href=3D"mailto:srinath2133@gmail.com" t=
arget=3D"_blank">srinath2133@gmail.com</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">Hi=
=C2=A0Julien,</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Wed, Apr 15, 2026 at 7:47=E2=80=AFPM Julien Tachoires &lt;<=
a href=3D"mailto:julien@tachoires.me" target=3D"_blank">julien@tachoires.me=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
Hi,<br>
<br>
One of our customer is experiencing an issue when executing CREATE TABLE<br=
>
.. LIKE .. INCLUDING ALL; on 14, the following kind of error happens:<br>
ERROR: cache lookup failed for attribute X of relation ZZZZZZ<br>
<br>
It seems to come from generateClonedExtStatsStmt(): get_attname()<br>
appears to be called with an attribute number (attnum) that does not<br>
exist.<br></blockquote><div><br>yeah, i was able to reproduce=C2=A0and also=
 check the flow which is the same<br>as you mentioned.<br></div></div></div=
></blockquote><div><br></div><div>I looked into this and the issue is in ge=
nerateClonedExtStatsStmt().<br>It passes the child&#39;s relation OID<br>to=
 get_attname() with attribute numbers from the parent&#39;s stxkeys.<br>Wit=
h dropped columns the attnums don&#39;t match.<br><br>Julien&#39;s patch fi=
xes that, it likely needs to be backported too.</div><div>=C2=A0</div><div>=
Regards,<br>Ayush</div><div><br></div><div>=C2=A0</div><div><br></div><div>=
<br></div><div><br></div><div>=C2=A0</div></div></div>
</div>

--0000000000007224e206500b412c--