From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: A failure in prepared_xacts test |
Date: | 2024-04-29 08:49:28 |
Message-ID: | CAMbWs4_gW-ZJ7o=f_NmcW96SvACCtZ2cqFqpR+XLUSpoZ4mKTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 29, 2024 at 1:11 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Up to now, we've only worried about whether tests running in parallel
> within a single test suite can interact. It's quite scary to think
> that the meson setup has expanded the possibility of interactions
> to our entire source tree. Maybe that was a bad idea and we should
> fix the meson infrastructure to not do that. I fear that otherwise,
> we'll get bit regularly by very-low-probability bugs of this kind.
I have the same concern. I suspect that the scan of pg_prepared_xacts
is not the only test that could cause problems when running in parallel
to other tests from the entire source tree.
Thanks
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | shveta malik | 2024-04-29 09:08:48 | Re: Synchronizing slots from primary to standby |
Previous Message | Heikki Linnakangas | 2024-04-29 08:38:17 | Re: Direct SSL connection with ALPN and HBA rules |