Re: test: avoid redundant standby catchup in 049_wait_for_lsn

From: Jobin Augustine <jobin(dot)augustine(at)percona(dot)com>
To: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: test: avoid redundant standby catchup in 049_wait_for_lsn
Date: 2026-09-30 04:24:22
Message-ID: CAEpZXfcWKayYHrFc=MKkk6nHTGeFZ6Gi3Z0OuAEJACU0P=0Mew@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Xuneng,

> Interestingly, is this a pressure test? Can you please elaborate a bit
> more on how the application tests it?
>
It was a custom coded application in Rust designed to demonstrate how this
feature can reduce connections in the connection pool (deadpool of Rust
with 16 connections in the pool), Because primary can commit asynchronously
and release the connection back to pool and then wait for standby. I don't
mind sharing the code, if that helps.

>
>
>> A client side workaround similar to the following is a temporary solution
>> for me for my tests:
>> ...
>>
>
> I think we better fix the page/segment header issue on the server side.
>

Agree, +1
We cannot expect every application to impliment workaround after
documenting the known problem
Thank you,
Jobin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Kim 2026-09-30 04:32:14 Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
Previous Message shihao zhong 2026-09-30 04:12:15 Two fixes for parallel query cleanup: DSM detach order and a stray statement timeout