Re: pg_catalog
От | Fabrízio de Royes Mello |
---|---|
Тема | Re: pg_catalog |
Дата | |
Msg-id | CAFcNs+r8XSCu8uwJVYodQh_35XVsSjvoXSvrr79EpsucW+R3Yg@mail.gmail.com обсуждение исходный текст |
Ответ на | pg_catalog (Graham Little <graham.little@aspone.co.uk>) |
Ответы |
Re: pg_catalog
|
Список | pgsql-hackers |
On Mon, Jan 28, 2013 at 10:24 AM, Graham Little <graham.little@aspone.co.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)
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
В списке pgsql-hackers по дате отправления: