| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | sdaekb(at)yandex(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. |
| Date: | 2026-06-16 03:46:26 |
| Message-ID: | ajDHEpkkfOx0NcSa@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 15, 2026 at 10:44:31PM +0500, Andrey Borodin wrote:
> Hi! Thanks for the report. Can you please give a bit more logs? This excerpt is
> missing errors from the startup process. And message from this process could shed
> a light on a root cause.
Looking at the set of changes in the range REL_14_22..REL_14_23, we
don't have many things related to recovery, so if you can provide more
details we will likely be able to point to a cause. Without more
information there is nothing that we can unfortunately do.
One thing that I suspect is some custom extension code that may live
outside of core. I have not heard about cases similar to the one
here, and it's been more than 4 weeks since this 14.23 has been
released.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2026-06-16 06:37:42 | Re: Fw:Re: Fw: ltree_compare in contrib/ltree/ltree_op.c overflows int32 on deep ltree comparisons, returning the wrong sign |
| Previous Message | Michael Paquier | 2026-06-15 23:24:51 | Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions = |