| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sajith Prabhakar Shetty <ssajith(at)blackduck(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
| Date: | 2025-05-16 12:51:43 |
| Message-ID: | 16974.1747399903@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Sajith Prabhakar Shetty <ssajith(at)blackduck(dot)com> writes:
> In my first test, I used pg_upgrade to upgrade the instance from 15 to 17, and in my second test, I created PG15 and PG17 separately from brew repo, I don’t think I am using debug build here.
Might be worth checking the brew recipes... it's common for packagers to
set the debug option for beta versions, and I could believe that whoever
packages PG for HomeBrew forgot to take that out again for 17.0.
But, assuming it's not that, could you put together a self-contained
test case that demos what you're seeing?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2025-05-16 14:50:42 | Re: BUG #18923: pg_dump 18beta1 fails to process complex table names |
| Previous Message | 萧鸿骏 | 2025-05-16 08:10:38 | Re: Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost |