From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Subject: | Re: Recent 027_streaming_regress.pl hangs |
Date: | 2024-07-25 22:10:29 |
Message-ID: | CA+hUKGJKMwMQSYKVBmna9mfF4Yu1TN=ABCuavCHxhjG08nDczg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 26, 2024 at 9:14 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Based on this, it seems fairly likely that crake is simply timing out
> as a consequence of intermittent heavy background activity.
Would it be better to keep going as long as progress is being made?
I.e. time out only when the relevant LSN stops advancing for N
seconds? Or something like that...
From | Date | Subject | |
---|---|---|---|
Next Message | Sami Imseih | 2024-07-25 22:27:15 | Re: Restart pg_usleep when interrupted |
Previous Message | Dave Cramer | 2024-07-25 21:52:41 | Re: Protocol question regarding Portal vs Cursor |