Re: pgsql: Do assorted mop-up in the planner.

Thanks for taking a look.

To add, although a slightly different signature, it looks like Bug #17769 is
also related to this commit b448f1c8d83f.

https://www.postgresql.org/message-id/17769-e4f7a5c9d84a80a7%40postgresql.org

=======
SQL
SELECT
FROM pg_catalog.pg_statio_all_tables AS ref_0,
     LATERAL (SELECT
              WHERE ref_0.schemaname = ref_0.relname) AS subq_0;


Checking (0736fc1ceb~16) - 3bef56e11650a33f70adeb6dd442bc2b48bb9b72 - Crash
Checking (0736fc1ceb~17) - b448f1c8d83f8b65e2f0080c556ee21a7076da25 - Crash
Checking (0736fc1ceb~18) - 2489d76c4906f4461a364ca8ad7e0751ead8aa0d - Success
Checking (0736fc1ceb~19) - ec7e053a98f39a9e3c7e6d35f0d2e83933882399 - Success
Checking (0736fc1ceb~20) - fe9e658f4d7fbc12d2b6a74c4ee90c73e53d68ef - Success

-
robins

On Thu, 2 Feb 2023 at 12:23, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Robins Tharakan <tharakan@gmail.com> writes:
> > This commit is causing occasional Asserts in my testing.
>
> Thanks!  I'm tired now, but will have a look tomorrow.
>
>                         regards, tom lane