Re: Re: [PATCHES] As proposed the complete changes to pg_trigger and pg_rewrite - Mailing list pgsql-hackers

From alfranio correia junior
Subject Re: Re: [PATCHES] As proposed the complete changes to pg_trigger and pg_rewrite
Date
Msg-id 4608FBF5.1060904@lsd.di.uminho.pt
Whole thread Raw
In response to Re: [PATCHES] As proposed the complete changes to pg_trigger and pg_rewrite  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
>>>
>>> Should these designations be more generic in case there are other uses
>>> for enabling/disabling groups of triggers?
>> That would be fine with me, I just wasn't able to come up with any 
>> sensible naming scheme other than replication related. Can you?
> 
> The best I could think of would be to create numbered groups of
> triggers, but because I can't think of any use for that, and no one else
> has, I think the patch is fine unchanged.

Instead of numbering, why don't you use names ?

------------------------------------------------------------------------

I did a similar patch a couple of years ago, but I put it away
as it required modifications to the database catalog.
I am glad to hear that modifications to make replication easier on top 
of PostgreSQL are being made.

Do you have any plans in introducing flags for other types of 
constraints and even sequences. Such modifications would be very useful 
for replication.

Best regards,

Alfranio.


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: notification payloads
Next
From: Andrew Dunstan
Date:
Subject: Re: notification payloads