| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Egor Chindyaskin <kyzevan23(at)mail(dot)ru>, Sascha Kuhl <yogidabanli(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Stack overflow issue |
| Date: | 2024-01-11 17:37:58 |
| Message-ID: | CA+TgmoZbw8ivGy5Ma3B0_AtBN8pg5ovrSXM_w_sChz6spTe=FQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 10, 2024 at 4:25 PM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> The problem with CommitTransactionCommand (or rather
> AbortCurrentTransaction() which has the same problem)
> and ShowTransactionStateRec is that they get called in a state where
> aborting can lead to a panic. If you add a "check_stack_depth()" to them
> and try to reproducer scripts that Egor posted, you still get a panic.
Hmm, that's unfortunate. I'm not sure what to do about that. But I'd
still suggest looking for a goto-free approach.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Xiaoran Wang | 2024-01-11 17:52:21 | Re: Recovering from detoast-related catcache invalidations |
| Previous Message | Magnus Hagander | 2024-01-11 17:00:42 | Re: Compile warnings in dbcommands.c building with meson |