| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lowell Hought <lowell(dot)hought(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 |
| Date: | 2025-06-14 22:26:37 |
| Message-ID: | 49486.1749939997@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Lowell Hought <lowell(dot)hought(at)gmail(dot)com> writes:
> Attached in three separate files.
Thanks. The only thing that's really obvious here is that the
rowcount estimates must be way off, because if the join outputs
were as small as the planner thinks, this query couldn't take
very long at all. I wonder whether your v17 installation is
lacking appropriate statistics. By now autovacuum should have
mostly filled that in even if you forgot to see to it when
transferring data --- but maybe you had larger-than-default
statistics targets in the v16 installation? Or some other
change to the default settings? I'd double-check that and
then do a manual ANALYZE of the whole database, and see if
anything changes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2025-06-15 01:23:41 | Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build |
| Previous Message | Lowell Hought | 2025-06-14 21:35:20 | Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 |