| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 'Richard Guo' <guofenglinux(at)gmail(dot)com> |
| Subject: | Re: recoveryCheck test failure on flaviventris |
| Date: | 2025-04-16 18:00:00 |
| Message-ID: | de984269-a1b0-421a-a8e4-5f47918898fb@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Kuroda-san,
16.04.2025 11:12, Hayato Kuroda (Fujitsu) wrote:
> Dear Richard, Alexander,
>
> FYI - I felt there is a same type of failure [1] for REL_17_STABLE, added in the wikipage.
> Feel free to revert it if I did something wrong.
>
> [1]:https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=prion&dt=2025-04-15%2016%3A16%3A06&stg=recovery-check
Thank you for adding that! (I'm a bit slow on analyzing new failures, but
I hope I could catch up on the weekend.)
I've just reformatted the record to match my script's [1] expectations.
[1] https://www.postgresql.org/message-id/b62f97b1-bbff-42cd-861f-c785f0774ab8%40gmail.com
Best regards,
Alexander Lakhin
Neon (https://neon.tech)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2025-04-16 18:07:45 | Re: A modest proposal: make parser/rewriter/planner inputs read-only |
| Previous Message | Pavel Stehule | 2025-04-16 17:50:44 | Re: Performance issues with v18 SQL-language-function changes |