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

From Jan Wieck
Subject Re: Proposal: Change of pg_trigger.tg_enabled and adding
Date
Msg-id 45B9523F.9080101@Yahoo.com
Whole thread Raw
In response to Re: Proposal: Change of pg_trigger.tg_enabled and adding pg_rewrite.ev_enabled  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: Proposal: Commit timestamp
Next
From: Richard Troy
Date:
Subject: Re: Proposal: Commit timestamp