Hi, David!
On Mon, Apr 7, 2025 at 12:15 PM David Rowley <dgrowle...@gmail.com> wrote:
>
> On Mon, 7 Apr 2025 at 19:39, Melanie Plageman <melanieplage...@gmail.com>
> wrote:
> > +++
> > C:/cirrus/build/testrun/pg_upgrade/002_pg_upgrade/data/results/subselect.out
> > 2025-04-04 14:47:20.358393500 +0000
> > @@ -2769,15 +2769,16 @@
> > EXPLAIN (COSTS OFF)
> > SELECT c.oid,c.relname FROM pg_class c JOIN pg_am a USING (oid)
> > WHERE c.oid IN (VALUES (1), (2));
> > - QUERY PLAN
> > ----------------------------------------------------------------
> > - Hash Join
> > - Hash Cond: (a.oid = c.oid)
> > - -> Seq Scan on pg_am a
> > - -> Hash
> > - -> Index Scan using pg_class_oid_index on pg_class c
> > - Index Cond: (oid = ANY ('{1,2}'::oid[]))
> > -(6 rows)
> > + QUERY PLAN
> > +---------------------------------------------------------
> > + Merge Join
> > + Merge Cond: (c.oid = a.oid)
> > + -> Index Scan using pg_class_oid_index on pg_class c
> > + Index Cond: (oid = ANY ('{1,2}'::oid[]))
> > + -> Sort
> > + Sort Key: a.oid
> > + -> Seq Scan on pg_am a
> > +(7 rows)
>
> Are these failures from patches applied to master prior to 3ba2cdaa?
Yes, these failures appears before 3ba2cdaa. Tom committed 3ba2cdaa
to fix the problem before I get into it [1].
Links.
1.
https://www.postgresql.org/message-id/srnuqlttuimzmvoulhsrbgvj4vnul6b65osswvua7sfkqsvmuy%40yg7apybpxp34
------
Regards,
Alexander Korotkov
Supabase
