| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: postgres_fdw test timeouts |
| Date: | 2023-12-03 06:00:15 |
| Message-ID: | CA+hUKGJAxrLP7rqGA2z1yLPvDUQqs5fvd1OYvKXAq8pYKc7+bg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Dec 3, 2023 at 6:00 PM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> I've managed to reproduce the failure locally when running postgres_fdw_x/
> regress in parallel (--num-processes 10). It reproduced for me on
> on 04a09ee94 (iterations 1, 2, 4), but not on 04a09ee94~1 (30 iterations
> passed).
>
> I'm going to investigate this case within days. Maybe we could find a
> better fix for the issue.
Thanks. One thing I can recommend to anyone trying to understand the
change is that you view it with:
git show --ignore-all-space 04a09ee
... because it changed a lot of indentation when wrapping a bunch of
stuff in a new for loop.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2023-12-03 10:13:57 | Re: SQL:2011 application time |
| Previous Message | Pavel Stehule | 2023-12-03 05:04:12 | Re: Schema variables - new implementation for Postgres 15 |