From: MichaelDBA <MichaelDBA@sqlexec.com>
To: Maxim Boguk <maxim.boguk@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.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: Sun, 1 Jan 2023 08:27:34 -0500
Message-ID: <2f7a8841-71c7-03e7-1bd5-2b1f95d24c16@sqlexec.com> (raw)
In-Reply-To: <CAK-MWwTRVNoDnjeKh-03cpubS9D1hhY-UofwYQChtLM2Y1EwWg@mail.gmail.com>
References: <CAK-MWwSfx7SmUQ=_rB4q61sE8uP6LqH-1wM0DSYyBadjBe9BDw@mail.gmail.com>
<20221231143203.GK1153@telsasoft.com>
<CAK-MWwTRVNoDnjeKh-03cpubS9D1hhY-UofwYQChtLM2Y1EwWg@mail.gmail.com>
Howdy,
Few additional questions:
1. How many concurrent, active connections are running when these BIND
problems occur? select count(*) from pg_stat_activity where state
in ('active','idle in transaction')
2. Are the queries using gigantic IN (<big list>) values?
3. Perhaps unrelated, but islog_temp_files turned on, and if so, do you
have a lot of logs related to that?
Regards,
Michael Vitale, just another PG DBA
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, pryzby@telsasoft.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: <2f7a8841-71c7-03e7-1bd5-2b1f95d24c16@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