From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |
Date: | 2025-08-21 18:17:27 |
Message-ID: | 2a3e4a8d-e8c2-46d6-ad7d-9e631ce6725e@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/21/25 09:51, hubert depesz lubaczewski wrote:
> On Thu, Aug 21, 2025 at 08:59:03AM -0700, Adrian Klaver wrote:
>> Getting to the bottom of the bag of ideas:
>> Have you looked at the OS system log for the time period involved?
>
> Yes. Mostly dmesg. Nothing interesting logged around the time.
>
>> You mentioned this seemed to involve PREPARE and DISCARD ALL.
>> Is this the same set of statements or is it all over the place?
>
> No. From what I can tell it's random sample.
>
>> Also it would be helpful to know what bouncer you are actually using and
>> what mode you are running in?
>
> pgBouncer, version 1.23.1. As for more... mostly transaction pooling.
> Applications go using transaction pooling, but people (dbas, ops) have
> session pooling.
Have you looked at?:
https://www.pgbouncer.org/changelog.html#pgbouncer-124x
To see if anything stands out.
Then there is:
https://www.pgbouncer.org/config.html#max_prepared_statements
The below may also be worth looking at:
https://github.com/pgbouncer/pgbouncer/pull/1144
I can't help thinking that there is a caching issue at stake, though
that is just a guess.
>
> Best regards,
>
> depesz
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Wilson | 2025-08-21 18:38:34 | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |
Previous Message | Adrian Klaver | 2025-08-21 17:43:02 | Re: Q: GRANT ... WITH ADMIN on PG 17 |