| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A test for replay of regression tests |
| Date: | 2022-02-02 03:14:04 |
| Message-ID: | CA+hUKG+Bncrfh0piJ83HUZ4cG+58TikGXwDux4sj7jvoMc=eNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 2, 2022 at 3:43 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > Seen again today on prairiedog. Erm, scratch that idea, HS feedback
> > interferes with test results. I guess max_standby_streaming_delay
> > should be increased to 'forever', like in the attached, since pg_dump
> > runs for a very long time on prairiedog:
>
> FWIW, I'd vote for keeping a finite timeout, but making it say
> ten minutes. If the thing gets stuck for some reason, you don't
> really want the test waiting forever. (Some buildfarm animals
> have overall-test-time limits, but I think it's not the default,
> and the behavior when that gets hit is pretty unfriendly anyway
> -- you don't get any report of the run at all.)
Ok, I've set it to 10 minutes. Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-02-02 03:33:09 | Re: Doc: CREATE_REPLICATION_SLOT command requires the plugin name |
| Previous Message | Amit Kapila | 2022-02-02 03:07:40 | Re: Design of pg_stat_subscription_workers vs pgstats |