Horton

Re: BUG #17035: assert after commit

RekGRpth <rekgrpth@gmail.com>

View thread View on postgr.es
From: RekGRpth <rekgrpth@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2021-05-26T13:54:03Z
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@sss.pgh.pa.us>:
>
> PG Bug reporting form <noreply@postgresql.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

Commits

  1. Use elog, not Assert, to report failure to provide an outer snapshot.

  2. Restore the portal-level snapshot after procedure COMMIT/ROLLBACK.