Tom Lane wrote:
Andrew Dunstan writes:
I thought we had fixed this in 8.3:
I think that behavior is intentional: plancache.c can deal with the plan
changing internally, but it doesn't expect that its callers could
survive the plan's argument datatypes changing underneath them.
Andrew Dunstan writes:
> I thought we had fixed this in 8.3:
I think that behavior is intentional: plancache.c can deal with the plan
changing internally, but it doesn't expect that its callers could
survive the plan's argument datatypes changing underneath them.
regards,
I thought we had fixed this in 8.3:
cap=# create table t1 (t varchar(40));
CREATE TABLE
cap=# create table t2 (t varchar(40));
CREATE TABLE
cap=# create function t1trig() returns trigger language plpgsql as
$$ begin insert into t2 values(new.t); return null; end; $$;
CREATE
