Re: pg_catalog

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Graham Little <graham(dot)little(at)aspone(dot)co(dot)uk>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_catalog
Date: 2013-01-28 13:02:58
Message-ID: CAFcNs+r8XSCu8uwJVYodQh_35XVsSjvoXSvrr79EpsucW+R3Yg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 28, 2013 at 10:24 AM, Graham Little <graham(dot)little(at)aspone(dot)co(dot)uk>
wrote:
>
> Hi,
>
>
>
> I have tried other sources but to no avail. Could someone please tell me
which tables in pg_catalog
> are effected by creating or dropping a trigger. If there is a work flow
diagram or source code location
> you want to point me to rather than listing them that will be fine also.

I don't know if its completely right, but when a trigger is created the
following catalog are affecteds:
- pg_trigger (new entry)
- pg_depend (new entry)
- pg_class (update relhastriggers column)

> Some plonker deleted some rows directly in the pg_triggers table …. I
need to fix it.

Maybe you simply DROP and CREATE trigger solve it...

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

In response to

  • pg_catalog at 2013-01-28 12:24:39 from Graham Little

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-01-28 13:11:12 Re: autovacuum not prioritising for-wraparound tables
Previous Message Graham Little 2013-01-28 12:24:39 pg_catalog