max.valjanski@gmail.com writes:
> # update ab_group set name=3D'Domain Controllerz' where id=3D466;
> ERROR: table row type and query-specified row type do not match
> =D0=9F=D0=9E=D0=94=D0=A0=D0=9E=D0=91=D0=9D=D0=9E=D0=A1=D0=A2=D0=98: Que=
ry provides a value for a dropped column at ordinal
> position 6.
> =D0=9A=D0=9E=D0=9D=D0=A2=D0=95=D0=9A=D0=A1=D0=A2: SQL statement "UPDATE=
ab_group SET name_gin =3D
> to_tsvector('simple', NEW.name) WHERE id =3D NEW.id AND NEW.name <>
> OLD.name"
> PL/pgSQL function update_group_name_gin() line 4 at SQL statement
Wait a minute ... the trigger is issuing another UPDATE on its
own table? Aren't you risking an infinite recursion?
Could we see the result of
select attname,atttypid,attnum,attisdropped from pg_attribute
where attrelid =3D 'ab_group'::regclass order by attnum;
Also the exact definitions of all triggers and rules for that table.
regards, tom lane
