| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Сергей Дм(dot) Апойченко <sdaekb(at)yandex(dot)ru> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, PostgreSQL mailing lists <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-17 23:27:28 |
| Message-ID: | ajMtYH_wRQa0zD-D@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jun 17, 2026 at 09:49:22PM +0500, Сергей Дм. Апойченко wrote:
> It doesn't seem to be a code error, but rather a configuration issue
> on the server itself. Given that I cannot provide any additional
> information and was unable to reproduce the error, I would like to
> close the ticket. Thank you for your response.
Okay, thanks for the update. The handling of multixacts during
recovery has already been tweaked a bit. I think that we are in a
good spot in terms of lock handling in the stable branches, but if you
still see something strange, please feel free to update this thread
with more information for investigation.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-06-18 01:03:40 | Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions = |
| Previous Message | Tom Lane | 2026-06-17 21:56:39 | Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct |