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: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17035: assert after commit
Date: 2021-05-26 13:54:03
Message-ID: CAPgh2mKzhcpjn1zfnT31FxOqc=CEfqEUg48DNvhunXXDscsH1A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ok, thanks. I only use SPI_execute_plan and before that commit all works fine
with bst regrds, Rek>pth

ср, 26 мая 2021 г. в 18:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > after this commit
> > https://github.com/postgres/postgres/commit/d18ee6f92d9a22b4fae57f515797b2196bf385c7
> > I got assert
> > TRAP: FailedAssertion("portal != NULL", File: "pquery.c", Line: 1758)
> > in my plugin
> > https://github.com/RekGRpth/pg_task
>
> I'm inclined to think that means you were doing something you
> should not have been doing. But without any details it's
> hard to say.
>
> regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Justin Pryzby 2021-05-26 14:21:08 Re: XX000: unknown type of jsonb container.
Previous Message Tom Lane 2021-05-26 13:52:31 Re: BUG #17035: assert after commit