Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M41231=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1UpEo4-00088H-AV
 for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jun 2013 09:36:00 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M41231=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1UpEo3-0001vc-QM
 for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jun 2013 09:35:59 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <ruralhunter@gmail.com>) id 1UpEo2-0001vN-HG
 for pgsql-admin@postgresql.org; Wed, 19 Jun 2013 09:35:58 +0000
Received: from mail-pa0-x235.google.com ([2607:f8b0:400e:c03::235])
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <ruralhunter@gmail.com>) id 1UpEnz-0004Kg-NT
 for pgsql-admin@postgresql.org; Wed, 19 Jun 2013 09:35:57 +0000
Received: by mail-pa0-f53.google.com with SMTP id tj12so4942513pac.26
 for <pgsql-admin@postgresql.org>; Wed, 19 Jun 2013 02:35:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject
 :content-type:content-transfer-encoding;
 bh=tnAq6b1vPzMMdmJenbTa8sSB4VwB9n75U7i3o3B8fVk=;
 b=zJrsJ46sSKpAqnHAfl2RYsvBHebvO9SNZfnqGHFaH9JjHl+7o+q0S+0Ef3eZ+yL1yG
 RgZ9VY8L2gKFiXHZOcGuYejbIQRQ4m1gWbwMnBoRl8NL9v/VXQ9ZUBKE0XV03zx1ROjw
 L9KO5vHez2x9b9DM4Qcy7iLEoRn+orAF9tJZvlnGp7ciNHcAfxe6yJajKSyVsusAPWzu
 L9UxL49Mgf4KiUB+rikPfz1srcDL++L54J8HZQ/spwMrQ0QvUARZhvuHGXV15bQ++hmB
 RC9S04txFYpshPQrK7sCM8B+bzlJITeslLO63zl56WgBRZEsD6L7IufLZ7hG16hlk/Dw
 c99A==
X-Received: by 10.66.159.234 with SMTP id xf10mr5865862pab.203.1371634554057;
 Wed, 19 Jun 2013 02:35:54 -0700 (PDT)
Received: from [192.168.1.16] ([116.226.82.25])
 by mx.google.com with ESMTPSA id v20sm24052976paj.4.2013.06.19.02.35.51
 for <pgsql-admin@postgresql.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 19 Jun 2013 02:35:53 -0700 (PDT)
Message-ID: <51C17B74.4070109@gmail.com>
Date: Wed, 19 Jun 2013 17:35:48 +0800
From: Rural Hunter <ruralhunter@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Why sequence grant is separated from table?
Content-Type: text/plain; charset=GB18030; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: 0.7 (/)
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

I really hate the error "permission denied for sequence xxxxx" when I 
grant on a table but forget to grant additionally on the related 
sequence to users. Can the permission of table and related sequences be 
merged?


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