Re: Proposal: Change of pg_trigger.tg_enabled and adding

From: José Orlando Pereira <jop(at)lsd(dot)di(dot)uminho(dot)pt>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <JanWieck(at)yahoo(dot)com>, Alfranio Correia <alfranio(at)lsd(dot)di(dot)uminho(dot)pt>
Subject: Re: Proposal: Change of pg_trigger.tg_enabled and adding
Date: 2007-02-21 16:09:56
Message-ID: 200702211609.57020.jop@lsd.di.uminho.pt
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Browse pgsql-hackers by date

  From Date Subject
Next Message José Orlando Pereira 2007-02-21 16:14:35 Re: Priorities for users or queries?
Previous Message Martijn van Oosterhout 2007-02-21 16:04:38 Re: Column storage positions