pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: MichaelDBA <MichaelDBA@sqlexec.com>
To: Maxim Boguk <maxim.boguk@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
Date: Thu, 5 Jan 2023 06:31:46 -0500
Message-ID: <103b95ea-75d1-0a1e-9fed-817c17f31b0f@sqlexec.com> (raw)
In-Reply-To: <CAK-MWwRxnjLTTTkM_muvBrHMoYYbT5xYFm=5cML9Q+SfRAwkXQ@mail.gmail.com>
References: <CAK-MWwSfx7SmUQ=_rB4q61sE8uP6LqH-1wM0DSYyBadjBe9BDw@mail.gmail.com>
	<CAK-MWwRxnjLTTTkM_muvBrHMoYYbT5xYFm=5cML9Q+SfRAwkXQ@mail.gmail.com>


What happens if you take pg_stat_statements out of the picture (remove 
from shared_preload_libraries)?  Does your BIND problem go away?

view thread (13+ messages)  latest in thread

Message-ID: <103b95ea-75d1-0a1e-9fed-817c17f31b0f@sqlexec.com>
Permalink:  ../103b95ea-75d1-0a1e-9fed-817c17f31b0f@sqlexec.com/
Also on:    postgresql.org/message-id/103b95ea-75d1-0a1e-9fed-817c17f31b0f@sqlexec.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-performance@postgresql.org
  Cc: MichaelDBA@sqlexec.com, maxim.boguk@gmail.com, pgsql-performance@lists.postgresql.org
  Subject: Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
  In-Reply-To: <103b95ea-75d1-0a1e-9fed-817c17f31b0f@sqlexec.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