Tom Lane wrote:
> So what I'm thinking is:
>
> 1. We can't redefine the SPI interface in back branches, so there's
> probably little alternative but to remove those Asserts there.
Committed this.
> 2. In HEAD, I think we should have SPI return a new SPI_OK_REWRITTEN
> code for this case, and have plpgsql respond to that by always setting
> found = false. With that, the Asserts can stay (in fact the new path
> should assert !mod_stmt, since it shouldn't have found any canSetTag
> query).
I'll look into this as a separate patch.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com