| From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
|---|---|
| To: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits) |
| Date: | 2023-01-05 11:46:49 |
| Message-ID: | 759b87bb-b3c7-6c39-4297-26a2777f9836@sqlexec.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Well if you find out for sure, please let me know. I'm very interested
in the outcome of this problem.
Maxim Boguk wrote on 1/5/2023 6:44 AM:
>
>
> On Thu, Jan 5, 2023 at 1:31 PM MichaelDBA <MichaelDBA(at)sqlexec(dot)com
> <mailto:MichaelDBA(at)sqlexec(dot)com>> wrote:
>
>
> What happens if you takepg_stat_statements out of the picture
> (remove from shared_preload_libraries)? Does your BIND problem go
> away?
>
>
> I didn't test this idea, because it requires restart of the database
> (it cannot be done quickly) and without pg_stat_statementsthere will
> be no adequate performance monitoring of the database.
> But I'm pretty sure that the issue will go away with
> pg_stat_statements disabled.
>
> --
> Maxim Boguk
> Senior Postgresql DBA
> https://dataegret.com/
>
> Phone UA: +380 99 143 0000
> Phone AU: +61 45 218 5678
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Wildish | 2023-01-06 21:09:54 | Max write throughput for single COPY |
| Previous Message | Maxim Boguk | 2023-01-05 11:44:33 | Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits) |