From: | alfranio correia junior <alfranio(at)lsd(dot)di(dot)uminho(dot)pt> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Re: [PATCHES] As proposed the complete changes to pg_trigger and pg_rewrite |
Date: | 2007-03-27 11:11:49 |
Message-ID: | 4608FBF5.1060904@lsd.di.uminho.pt |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
>>>
>>> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-03-27 11:16:45 | Re: notification payloads |
Previous Message | Andrew Dunstan | 2007-03-27 11:11:03 | Re: notification payloads |
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2007-03-27 12:27:01 | Replace badly licensed blf.c in pgcrypto |
Previous Message | Gregory Stark | 2007-03-27 11:06:26 | Re: Numeric patch to add special-case representations for < 8 bytes |