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 45BA773F.9070101@Yahoo.com
Whole thread Raw
In response to Re: Proposal: Change of pg_trigger.tg_enabled and adding pg_rewrite.ev_enabled  (Jim Nasby <decibel@decibel.org>)
Responses Re: Proposal: Change of pg_trigger.tg_enabled and adding  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 1/26/2007 4:40 PM, Jim Nasby wrote:
> On Jan 25, 2007, at 5:33 PM, Jan Wieck wrote:
>> A new per session GUC variable, restricted to superusers, will  
>> define if the session is in origin or replica mode.
> 
> It would be nice if we had a separate role for replication services  
> so that we weren't exposing superuser so much. IIRC Oracle even uses  
> 2 roles; one for administration of replication and one that the  
> replication code actually runs under.

So you think about another flag in pg_shadow? Would work for me.


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: Tom Lane
Date:
Subject: Re: Proposal: Snapshot cloning
Next
From: Jan Wieck
Date:
Subject: Re: Proposal: Change of pg_trigger.tg_enabled and adding