Re: Proposal: Change of pg_trigger.tg_enabled and adding - Mailing list pgsql-hackers

From José Orlando Pereira
Subject Re: Proposal: Change of pg_trigger.tg_enabled and adding
Date
Msg-id 200702211609.57020.jop@lsd.di.uminho.pt
Whole thread Raw
List pgsql-hackers
Jan Wieck wrote:
> On 1/25/2007 7:33 PM, Tom Lane wrote:
> >
> >         1       fires always
> >         0       fires never
> >         N       fires in "Normal" mode
> >         R       fires in "Replica" mode
> >         other letters available for other future mode values?
> > 
> > If you consistently think of "origin" and "replica" modes then the
> > original proposal is better (using both 0 and O would be Real Bad),
> > but your use of "normal" and "replica" in the followup makes me wonder
> > which terminology is more common.
> 
> Yeah, I tried for a long time to stay away from terms like master and
> slave ... but in the end people don't understand you if you talk about
> origin and subscriber or replica. That's how this inconsistent terminology 
> slipped into my vocabulary.    
>
> I personally don't care about the particular values. I could live with A, B,
> C, D. If people find 1, 0, N, R more explanatory, fine. 

Hi, 

Regardless of the actual namiing, we at the GORDA project strongly support 
this feature. In fact, our current prototype does this, although we do not 
allow fine grained configuration of which triggers get deactivated by 
the "replica mode". It is hardcoded.

(Sorry for being so late to the party, but the subject hasn't initially caught 
our attention.)

Regards,

-- 
Jose Orlando Pereira


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Column storage positions
Next
From: José Orlando Pereira
Date:
Subject: Re: Priorities for users or queries?