| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | nigel(at)oscsales(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17730: Trigger Issue |
| Date: | 2022-12-23 18:45:11 |
| Message-ID: | 2758407.1671821111@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-12-23 18:45:59 | Re: BUG #17730: Trigger Issue |
| Previous Message | Patrick Headley | 2022-12-23 17:50:25 | Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE |