> > Well, that wouldn't explain why it doesn't work on partitioned tables.
> > I am under the impression that it should.
> >
> > Derek, can cou share the pg_stats entries for the partitioned table?
>
> There are no entries in pg_stats for the parent table until after I manually
> run an analy
> > We recently performed an upgrade from pg14 (14.18) to pg16 (16.9) and
> > performed the analyze-in-stages post upgrade. It has been noticed that
> > some plans changed to use hash joins instead of nested loops. Further
> > investigation found it was because the parent table of partitioned
We recently performed an upgrade from pg14 (14.18) to pg16 (16.9) and performed
the analyze-in-stages post upgrade. It has been noticed that some plans
changed to use hash joins instead of nested loops. Further investigation found
it was because the parent table of partitioned tables did no
We recently performed an upgrade from pg14 (14.18) to pg16 (16.9) and performed
the analyze-in-stages post upgrade. It has been noticed that some plans
changed to use hash joins instead of nested loops. Further investigation found
it was because the parent table of partitioned tables did not
rotection -fcf-protection
CFLAGS_SL = -fPIC
LDFLAGS = -Wl,--as-needed -L/usr/lib64 -L/usr/lib -L/usr/lib64 -Wl,--as-needed
-Wl,-rpath,'/usr/pgsql-16/lib',--enable-new-dtags
LDFLAGS_EX =
LDFLAGS_SL =
LIBS = -lpgcommon -lpgport -lselinux -lzstd -llz4 -lxslt -lxml2 -lpam -lssl
-lcrypto -lgssa
Hello All,
We are getting a segmentation fault which seems to be specific to pg16 on
redhat 8. Tested on pg14 and pg15 with no problems. Also tested with pg16 on
redhat 9 - no issues. The developer determined that it is specific to select
into a defined variable within a function. We have a
