pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Shlok Kyal <shlok.kyal.oss@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: undetected deadlock in ALTER SUBSCRIPTION ... REFRESH PUBLICATION
Date: Tue, 5 Dec 2023 12:48:31 +0100
Message-ID: <a2e22743-3bb6-8e94-10ed-478e3e25e65a@enterprisedb.com> (raw)
In-Reply-To: <CANhcyEUka292SDPM1+WngRLmGw1UvD15gABWffZdFApKjbsY9Q@mail.gmail.com>
References: <d291bb50-12c4-e8af-2af2-7bb9bb4d8e3e@enterprisedb.com>
	<CAA4eK1LHD3ZHqyK2GcSw=fqCPr26yP2GL9niQbY8ems68D1Z9A@mail.gmail.com>
	<8948e4a2-fec7-8a61-9ace-2537cee3ef6f@enterprisedb.com>
	<CAA4eK1Kj6THmgXZ98d8rxAJa+V1KGS79KgqVve5i0Oyn+=tbMw@mail.gmail.com>
	<69e9a1af-a315-8b05-0674-2cc53bf27682@enterprisedb.com>
	<CAA4eK1L4wWiFnhDYhGMv-M4GTR6Xg13xoaSjhUm+YzFaP3nxUQ@mail.gmail.com>
	<9afab261-94a7-3e58-f0fb-040e45f42aa5@enterprisedb.com>
	<CANhcyEWtf6h5Ati69nbPoFXvFjfFsfrCekajWC=7JVnD0=cEfw@mail.gmail.com>
	<CANhcyEWxjwHXka+A+9PLJqpvEa5fZXD5Du1cW1QqzAxjdBhrmg@mail.gmail.com>
	<CAA4eK1KgyHAvDOPQgUdehSwUqDr0WxWtjxR5BHOMYkYaD2QZmA@mail.gmail.com>
	<CANhcyEXKW7LjPrBBc_ttxxeFrJBQQ=GbGCfZKcy0-6_8ejnJcg@mail.gmail.com>
	<CAA4eK1KKgA+j4z2XYkAZh5cEzAUEdKw0-u96bu5a9PBbZumS7Q@mail.gmail.com>
	<c4029baf-693d-4bb5-7c57-5bfcdc5572ff@enterprisedb.com>
	<CANhcyEUka292SDPM1+WngRLmGw1UvD15gABWffZdFApKjbsY9Q@mail.gmail.com>

On 12/5/23 08:14, Shlok Kyal wrote:
> Hi,
> 
>> As for the test results, I very much doubt the differences are not
>> caused simply by random timing variations, or something like that. And I
>> don't understand what "Performance Machine Linux" is, considering those
>> timings are slower than the other two machines.
> 
> The machine has Total Memory of 755.536 GB, 120 CPUs and RHEL 7 Operating System
> Also find the detailed info of the performance machine attached.
> 

Thanks for the info. I don't think the tests really benefit from this
much resources, I would be rather surprised if it was faster beyond 8
cores or so. The CPU frequency likely matters much more. Which probably
explains why this machine was the slowest.

Also, I wonder how much the results vary between the runs. I suppose you
only did s single run for each, right?

regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





view thread (23+ messages)  latest in thread

Message-ID: <a2e22743-3bb6-8e94-10ed-478e3e25e65a@enterprisedb.com>
Permalink:  ../a2e22743-3bb6-8e94-10ed-478e3e25e65a@enterprisedb.com/
Also on:    postgresql.org/message-id/a2e22743-3bb6-8e94-10ed-478e3e25e65a@enterprisedb.com

 · 

reply

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: tomas.vondra@enterprisedb.com, shlok.kyal.oss@gmail.com, amit.kapila16@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: undetected deadlock in ALTER SUBSCRIPTION ... REFRESH PUBLICATION
  In-Reply-To: <a2e22743-3bb6-8e94-10ed-478e3e25e65a@enterprisedb.com>

* 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