From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tharakan, Robins <tharar@amazon.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Massey, Sean <mssysm@amazon.com>
Subject: Re: track_planning causing performance regression
Date: Thu, 17 Sep 2020 23:43:09 -0400
Message-ID: <381870.1600400589@sss.pgh.pa.us> (raw)
In-Reply-To: <abd68940967343acb92f9554688809a4@EX13D05UWC001.ant.amazon.com>
References: <abd68940967343acb92f9554688809a4@EX13D05UWC001.ant.amazon.com>
"Tharakan, Robins" <tharar@amazon.com> writes:
>> During fully-cached SELECT-only test using pgbench, Postgres v13Beta1
>> shows ~45% performance drop [2] at high DB connection counts (when
>> compared with v12.3)
> It'd be great if we could also give credit to "Sean Massey" for this find.
I poked through my Postgres inbox, and couldn't find any previous
mail from or mentioning a Sean Massey.
While there's not much of a formal policy around this, we usually limit
ourselves to crediting people who have directly interacted with the PG
community. I'm aware that there's more than a few cases where someone
talks to the community on behalf of a company-internal team ... but
since we have little visibility into such situations, whoever's doing
the talking gets all the credit.
Given that background, it seems like crediting Sean here would be
slightly unfair special treatment. I'd encourage him to join the
mailing lists and be part of the community directly --- then we'll
definitely know what he's contributed.
regards, tom lane
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, tharar@amazon.com, mssysm@amazon.com
Subject: Re: track_planning causing performance regression
In-Reply-To: <381870.1600400589@sss.pgh.pa.us>
* 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