From: Tom Lane <tgl@sss.pgh.pa.us>
To: nigel@oscsales.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17730: Trigger Issue
In-reply-to: <17730-725d70639da4fd31@postgresql.org>
References: <17730-725d70639da4fd31@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 23 Dec 2022 17:09:18 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2758406.1671821111.1@sss.pgh.pa.us>
Date: Fri, 23 Dec 2022 13:45:11 -0500
Message-ID: <2758407.1671821111@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2758407.1671821111%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I have cloned a trigger from another table by inserting new rows into the
> pg_catalog.pg_triggers but the trigger is not working and the following
> querry -
> select pg_get_triggerdef(t.oid)
> from pg_catalog.pg_trigger t
> returns the error 
> cache lookup failed for attribute 7 of relation 1682781.

It's highly unlikely that this is a Postgres bug.
It sounds more like you fat-fingered your manual catalog changes.
(Why didn't you use CREATE TRIGGER instead?  Manual mucking
about in the catalogs is not for the inexpert.)

> Is there something else I need to change ?

[ shrug... ]  When you have not shown us exactly what you did,
that's an unanswerable question.

			regards, tom lane