Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M40821=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1ULSJC-0005VV-FS
	for pgsql-admin@arkaria.postgresql.org; Fri, 29 Mar 2013 05:57:02 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M40821=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1ULSJB-0008Qz-V6
	for pgsql-admin@arkaria.postgresql.org; Fri, 29 Mar 2013 05:57:02 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ruralhunter@gmail.com>) id 1ULSJB-0008Qu-9g
	for pgsql-admin@postgresql.org; Fri, 29 Mar 2013 05:57:01 +0000
Received: from mail-pd0-f175.google.com ([209.85.192.175])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ruralhunter@gmail.com>) id 1ULSJ7-0006Kv-IU
	for pgsql-admin@postgresql.org; Fri, 29 Mar 2013 05:57:01 +0000
Received: by mail-pd0-f175.google.com with SMTP id t10so128294pdi.20
	for <pgsql-admin@postgresql.org>; Thu, 28 Mar 2013 22:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=x-received:message-id:date:from:user-agent:mime-version:to:subject
	:content-type:content-transfer-encoding;
	bh=mx3Hy7loRIQi3Pkm+vdboETerB5KGCZRjISamvyEI4w=;
	b=wNMpVGPoc4mu+mMMsk2+i1omZsJhtPFWipeSdJqFcG4SODoLDfKpJ68O+/dZvroarw
	Q5A+9nSW4optHauD0bwOEUtOp/1jRGFRIgJmyjiduxB4KzHBk0qN6CLNCNRYiLVTYhNr
	j6er9rKIxLoY21B+/Xb7vhPMdXVUaHF4Ahb6wj9dd96meWatriD1x7bo49n1xZJ3K6P0
	et+2oU5XD5hQYdl1QzmMAMPitDGd87aH9ldCmiE4h5S2jqHnsGKh4oBX42wWG5jPusR1
	HWbgN9G8/cJSNBivp4dyPvtCO6Je6KgYzWqoJ9yWuNiJ84thajxeAa5NjRdHreBTUVjj
	iYKg==
X-Received: by 10.68.231.70 with SMTP id te6mr1942873pbc.159.1364536616254;
	Thu, 28 Mar 2013 22:56:56 -0700 (PDT)
Received: from [192.168.1.5] ([116.226.40.101])
	by mx.google.com with ESMTPS id to7sm2168537pab.0.2013.03.28.22.56.53
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 28 Mar 2013 22:56:55 -0700 (PDT)
Message-ID: <51552D2A.4090903@gmail.com>
Date: Fri, 29 Mar 2013 13:56:58 +0800
From: Rural Hunter <ruralhunter@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Grant tables cascade to sequence?
Content-Type: text/plain; charset=GB18030; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi,

I encounter the same issue often: Granted update/insert to an user but 
forgot to grant it on the related sequence. It's hard to understand that 
an user has write access on table but not on necessary sequences. I 
think the grant on tables should cascade to related sequences. What do 
you think?


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin