Re: BUG #17730: Trigger Issue

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: nigel(at)oscsales(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17730: Trigger Issue
Date: 2022-12-23 18:45:59
Message-ID: CAKFQuwYWOavq2sVdcdYXafyWYTrH4t_NafryJjsEb6=46K7ZWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Dec 23, 2022 at 10:13 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 17730
> Logged by: n d
> Email address: nigel(at)oscsales(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Windows
> Description:
>
> 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.
> Is there something else I need to change ?
>

This is not a valid bug report - if you decide to forgo using CREATE
TRIGGER to create a valid trigger in your database the problems that you
cause are not bugs and you probably shouldn't expect others to take an
interest in unbreaking your system. In any case you should seek any
desired assistance on the -general mailing list. Or, better yet, undo what
you did and go and do things correctly instead and hope that is sufficient.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2022-12-26 06:50:52 BUG #17731: Server doesn't start after abnormal shutdown while creating unlogged tables
Previous Message Tom Lane 2022-12-23 18:45:11 Re: BUG #17730: Trigger Issue