Re: Two-phase commit security restrictions

From: David Garamond <lists(at)zara(dot)6(dot)isreserved(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Two-phase commit security restrictions
Date: 2004-10-14 02:45:31
Message-ID: 416DE84B.9040507@zara.6.isreserved.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Oliver Jowett wrote:
> Heikki Linnakangas wrote:
>
>> 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.
>
> Doesn't this break recovery? The TM needs to find all outstanding GIDs
> for a particular resource.

Isn't it the TM's job to remember all the outstanding GIDs? But it would
be nice to ask each RM too, I guess.

--
dave

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Jowett 2004-10-14 03:14:06 Re: Two-phase commit security restrictions
Previous Message Tatsuo Ishii 2004-10-14 02:32:31 Re: [COMMITTERS] pgsql: Fix breakage in hashjoin from recent