1

(1 row)

-- a CLOBBER_CACHE_ALWAYS build will report this error with a different

-- context stack than other builds, so suppress context output

\set SHOW_CONTEXT never

select getf1(row(1,2)::two_int8s);

ERROR: record "x" has no field "f1"

select getf1(row(1,2));

getf1

-------

alter table mutable drop column f1;

alter table mutable add column f1 float8;

-- currently, this fails due to cached plan for "r.f1 + 1" expression

select sillyaddone(42);

ERROR: type of parameter 4 (double precision) does not match that when preparing the plan (integer)

CONTEXT: PL/pgSQL function sillyaddone(integer) line 1 at RETURN

-- select sillyaddone(42);

\c -

-- but it's OK after a reconnect

select sillyaddone(42);

(1 row)

alter table mutable drop column f3;

-- a CLOBBER_CACHE_ALWAYS build will report this error with a different

-- context stack than other builds, so suppress context output

\set SHOW_CONTEXT never

select getf3(null::mutable); -- fails again

ERROR: record "x" has no field "f3"

-- check access to system columns in a record variable

create function sillytrig() returns trigger language plpgsql as

$$begin

$$begin returnx.f1; end $$;

select getf1(1);

select getf1(row(1,2));

\set SHOW_CONTEXT never

select getf1(row(1,2)::two_int8s);

\set SHOW_CONTEXT errors

select getf1(row(1,2));

altertable mutable add column f1 float8;

select sillyaddone(42);

\c-

select sillyaddone(42);

altertable mutable add column f3int;

select getf3(null::mutable);-- now it works

altertable mutable drop column f3;

\set SHOW_CONTEXT never

select getf3(null::mutable);-- fails again

\set SHOW_CONTEXT errors