Re: Two-phase commit security restrictions - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Two-phase commit security restrictions
Date
Msg-id 200410131439.49237.josh@agliodbs.com
Whole thread Raw
In response to Two-phase commit security restrictions  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
Heikki,

> Another approach I've been thinking about is to allow anyone that knows
> the (user-supplied) global transaction identifier to finish the
> transaction, and hide the gids of running transactions from regular users.
> That way, the gid acts as a secret token that's only known by the
> transaction manager, much like the cancel key.

I agree with Tom; this is just inviting trouble.   Restrict it to the original 
user and the superuser.    Since any 3rd-party transaction manager (such as 
CJDBC) would use a single user to manage the transactions, I don't see that 
this restriction is a problem.

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Two-phase commit security restrictions
Next
From: Martha Chronopoulou
Date:
Subject: implementing another hash join...