From: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Add two missing tests in 035_standby_logical_decoding.pl |
Date: | 2023-04-25 07:25:39 |
Message-ID: | d26cdb6e-42c5-ce5a-3f26-54e496873cec@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 4/25/23 6:43 AM, Amit Kapila wrote:
> On Mon, Apr 24, 2023 at 5:38 PM Drouvot, Bertrand
> <bertranddrouvot(dot)pg(at)gmail(dot)com> wrote:
>>
>> We are waiting here at a maximum for 10 * $default_timeout (means 3 minutes) before
>> we time out. Would you prefer to wait more than 3 minutes at a maximum?
>>
>
> No, because I don't know what would be a suitable timeout here.
Yeah, I understand that. On the other hand, there is other places that
rely on a timeout, for example:
- wait_for_catchup(), wait_for_slot_catchup(),
wait_for_subscription_sync() by making use of poll_query_until.
- wait_for_log() by setting a max_attempts.
Couldn't we have the same concern for those ones? (aka be suitable on
slower machines).
> At
> this stage, I don't have a good idea on how to implement this test in
> a better way. Can we split this into a separate patch as the first
> test is a bit straightforward, we can push that one and then
> brainstorm on if there is a better way to test this functionality.
>
I created a dedicated v4-0002-Add-retained-WAL-test-in-035_standby_logical_deco.patch
just shared up-thread.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | torikoshia | 2023-04-25 07:38:16 | Allow pg_archivecleanup to remove backup history files |
Previous Message | Drouvot, Bertrand | 2023-04-25 07:19:43 | Re: Add two missing tests in 035_standby_logical_decoding.pl |