Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e95LbuJ70724 for ; Thu, 5 Oct 2000 17:37:56 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e95LboB17231; Thu, 5 Oct 2000 17:37:50 -0400 (EDT) To: "Saltsgaver, Scott" cc: "'pgsql-sql@postgresql.org'" Subject: Re: Granting of permissions on tables In-reply-to: <7283DE19D141D111AD0E00A0C95B195503A59E73@mail2.aiinet.com> References: <7283DE19D141D111AD0E00A0C95B195503A59E73@mail2.aiinet.com> Comments: In-reply-to "Saltsgaver, Scott" message dated "Thu, 05 Oct 2000 17:12:54 -0400" Date: Thu, 05 Oct 2000 17:37:49 -0400 Message-ID: <17228.970781869@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/72 "Saltsgaver, Scott" writes: > Is this a bug or desired behavior? I would imagine since I owned the tables > and then granted permissions to another user, I wouldn't lose my > permissions. It's a bug, or at least a misfeature. As long as you haven't done any explicit grants or revokes, 7.0 uses an implicit access control list that grants all privileges to the owner and none to anyone else. However, the moment you do any explicit grant/revoke, that implicit ACL entry for the owner isn't used anymore. You have to explicitly grant rights to yourself again :-(. You don't need superuser help to do this, you just have to do GRANT ALL ON table TO yourself as the table owner. But it's stupid to have to do that when it's supposed to be the default condition. Fixed for 7.1. regards, tom lane