| From: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Failures in constraints regression test, "read only 0 of 8192 bytes" |
| Date: | 2024-03-08 13:40:00 |
| Message-ID: | 2746777.mvXUDI8C0e@aivenlaptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le vendredi 8 mars 2024, 14:36:48 CET Tomas Vondra a écrit :
> > My guess would be 8af25652489, as it's the only storage-related commit.
> >
> > I'm currently running tests to verify this.
>
> Yup, the breakage starts with this commit. I haven't looked into the
> root cause, or whether the commit maybe just made some pre-existing
> issue easier to hit. Also, I haven't followed the discussion on the
> pgsql-bugs thread [1], maybe there are some interesting findings.
>
If that happens only on HEAD and not on 16, and doesn't involve WAL replay,
then it's not the same bug.
--
Ronan Dunklau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2024-03-08 13:41:52 | Re: Support a wildcard in backtrace_functions |
| Previous Message | Tomas Vondra | 2024-03-08 13:36:48 | Re: Failures in constraints regression test, "read only 0 of 8192 bytes" |