pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: KaiGai Kohei <kaigai@kaigai.gr.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PATCH] unalias of ACL_SELECT_FOR_UPDATE
Date: Sun, 19 Apr 2009 10:41:26 +0300
Message-ID: <49EAD5A6.4010601@enterprisedb.com> (raw)
In-Reply-To: <49EA7E4D.6060109@kaigai.gr.jp>
References: <49E809F6.8070008@ak.jp.nec.com>
	<49E8133A.7090601@enterprisedb.com>
	<49E81EA1.2060202@ak.jp.nec.com>
	<20069.1239977115@sss.pgh.pa.us>
	<49E91AE4.9020404@kaigai.gr.jp>
	<49E974AD.3020602@enterprisedb.com>
	<13982.1240056219@sss.pgh.pa.us>
	<49E9D5B6.9050406@enterprisedb.com>
	<49EA7E4D.6060109@kaigai.gr.jp>

KaiGai Kohei wrote:
> However, ACL_UPDATE and ACL_SELECT_FOR_UPDATE internally shares same bit
> so SE-PostgreSQL cannot discriminate between UPDATE and SELECT FOR UPDATE
> or SHARE.

Why should it discriminate between them?

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com



view thread (26+ messages)  latest in thread

Message-ID: <49EAD5A6.4010601@enterprisedb.com>
Permalink:  ../49EAD5A6.4010601@enterprisedb.com/
Also on:    postgresql.org/message-id/49EAD5A6.4010601@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: heikki.linnakangas@enterprisedb.com, kaigai@kaigai.gr.jp, tgl@sss.pgh.pa.us, kaigai@ak.jp.nec.com
  Subject: Re: [PATCH] unalias of ACL_SELECT_FOR_UPDATE
  In-Reply-To: <49EAD5A6.4010601@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox