| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Anton Voloshin <a(dot)voloshin(at)postgrespro(dot)ru>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 039_end_of_wal: error in "xl_tot_len zero" test |
| Date: | 2024-05-12 20:58:35 |
| Message-ID: | CAApHDvqjviT1zwums=XSGDh_=w5_rYhnHGCD=Dwpj7A7bzWvvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 6 May 2024 at 15:06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> My best guess is that that changed the amount of WAL generated by
> initdb just enough to make the problem reproduce on this animal.
> However, why's it *only* happening on this animal? The amount of
> WAL we generate isn't all that system-specific.
I'd say that's a good theory as it's now passing again [1] after the
recent system_views.sql change done in 521a7156ab.
David
[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2024-05-06%2017%3A43%3A38
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2024-05-12 21:23:42 | Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. |
| Previous Message | Peter Eisentraut | 2024-05-12 20:33:42 | Re: elog/ereport VS misleading backtrace_function function address |