RE: Big performance slowdown from 11.2 to 13.3
От | ldh@laurent-hasson.com |
---|---|
Тема | RE: Big performance slowdown from 11.2 to 13.3 |
Дата | |
Msg-id | MN2PR15MB25608160A30B6D34BE1489BB85E49@MN2PR15MB2560.namprd15.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Big performance slowdown from 11.2 to 13.3 (Peter Geoghegan <pg@bowt.ie>) |
Список | pgsql-performance |
-----Original Message----- From: Peter Geoghegan <pg@bowt.ie> Sent: Thursday, July 22, 2021 12:14 To: Tom Lane <tgl@sss.pgh.pa.us> Cc: Jeff Davis <pgsql@j-davis.com>; ldh@laurent-hasson.com; David Rowley <dgrowleyml@gmail.com>; Justin Pryzby <pryzby@telsasoft.com>;pgsql-performance@postgresql.org Subject: Re: Big performance slowdown from 11.2 to 13.3 On Thu, Jul 22, 2021 at 8:45 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > That is ... weird. Maybe you have found a bug in the spill-to-disk > logic; it's quite new after all. Can you extract a self-contained > test case that behaves this way? I wonder if this has something to do with the way that the input data is clustered. I recall noticing that that could significantlyalter the behavior of HashAggs as of Postgres 13. -- Peter Geoghegan I could execute that test and re-cluster against the index. But I believe that's already done? Let me check. Thank you, Laurent.
В списке pgsql-performance по дате отправления: