From: Tom Lane <tgl@sss.pgh.pa.us>
To: sofoklis24@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16730: Create table like with inheritance and self
 referencing index
In-reply-to: <16730-b902f7e6e0276b30@postgresql.org>
References: <16730-b902f7e6e0276b30@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 19 Nov 2020 15:41:24 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1214696.1605816636.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 19 Nov 2020 15:10:36 -0500
Message-ID: <1214697.1605816636@sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> The following simplified example used to work on previous versions, but =
not
> on 10.15, we tested it again on version 10.11 and it works.

Hmph.  Apparently I was too careless about the order of execution of
the sub-commands created by a LIKE clause.

I pushed this patch:

https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dpatch;h=3D513db7=
b7004c8d1fa15dea4747a32cbc8f9621ef

which takes care of the particular case you show, but now I wonder
if there are other issues lurking nearby.  If you're in a position
to test this and see if it fixes your real application, please do.

Thanks for the report!

			regards, tom lane