Re: BUG #17035: assert after commit

From: RekGRpth <rekgrpth(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17035: assert after commit
Date: 2021-05-27 03:00:59
Message-ID: CAPgh2mKqhomO0O0ciMc57sp13Jp0hZCLdR7MbL_mEvT3VrbT1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ok, I see. But I use SPI_execute_plan in background worker and no
ActivePortal there
with bst regrds, Rek>pth

ср, 26 мая 2021 г. в 22:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > Hmm, see for example [1] which is doing SPI_prepare_my() [2] and then
> > SPI_execute_plan_my() ... Does the SPI interface really require that you
> > create an ActivePortal in the SPI-calling code?
>
> The expectation is that the calling code is already executing inside
> some Portal. If it isn't, it's incumbent on the caller to set up
> an adequate substitute environment, in particular a transaction
> snapshot. The only thing 84f5c2908 changed is that now you get
> a guaranteed failure if you neglect to provide that, rather than
> failing only in corner cases.
>
> Possibly we should change that Assert to an elog that tries to
> make it clear that the blame is on the caller.
>
> regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-05-27 03:09:00 Re: BUG #17036: generated column cann't modifyed auto when update
Previous Message 德哥 2021-05-27 02:47:59 Re:Re: BUG #17036: generated column cann't modifyed auto when update