From: Tom Lane <tgl@sss.pgh.pa.us>
To: nigel@oscsales.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17730: Trigger Issue
Date: Fri, 23 Dec 2022 13:45:11 -0500
Message-ID: <2758407.1671821111@sss.pgh.pa.us> (raw)
In-Reply-To: <17730-725d70639da4fd31@postgresql.org>
References: <17730-725d70639da4fd31@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, nigel@oscsales.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17730: Trigger Issue
In-Reply-To: <2758407.1671821111@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox