From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: ldh@laurent-hasson.com <ldh@laurent-hasson.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Big performance slowdown from 11.2 to 13.3
Date: Thu, 22 Jul 2021 13:56:54 -0400
Message-ID: <202107221756.opvnumaebyht@alvherre.pgsql> (raw)
In-Reply-To: <MN2PR15MB2560A2F486FE1ACB520ECCBD85E49@MN2PR15MB2560.namprd15.prod.outlook.com>
On 2021-Jul-22, ldh@laurent-hasson.com wrote:
> Yes, agreed Peter... The "lower priority" issue was mentioned, but not
> in terms of the applicability of the fix overall. Personally, I would
> prefer going the size_t route vs int/long/int64 in C/C++/. Of course,
> as a user, I'd love a patch on V13 and something cleaner in V14.
Just to clarify our terminology here. "A patch" means any kind of
change to the source code, regardless of its cleanliness or
applicability to versions deemed stable. You can have one patch which
is a ugly hack for a stable version that can't have invasive changes,
and another patch which is a clean, more maintainable version of a
totally different fix for the version in development. We use the same
word, "patch", for both types of source code changes.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@alvh.no-ip.org, ldh@laurent-hasson.com, pg@bowt.ie, pryzby@telsasoft.com, tgl@sss.pgh.pa.us, dgrowleyml@gmail.com
Subject: Re: Big performance slowdown from 11.2 to 13.3
In-Reply-To: <202107221756.opvnumaebyht@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox