Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cdLat-0003WZ-Ch for pgsql-admin@arkaria.postgresql.org; Mon, 13 Feb 2017 18:43:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cdLas-00085W-Ey for pgsql-admin@arkaria.postgresql.org; Mon, 13 Feb 2017 18:43:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cdLar-00085P-Uu for pgsql-admin@postgresql.org; Mon, 13 Feb 2017 18:43:22 +0000 Received: from mail-qt0-x231.google.com ([2607:f8b0:400d:c0d::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cdLak-0008EL-FX for pgsql-admin@postgresql.org; Mon, 13 Feb 2017 18:43:21 +0000 Received: by mail-qt0-x231.google.com with SMTP id k15so91618652qtg.3 for ; Mon, 13 Feb 2017 10:43:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:user-agent:mime-version; bh=oVvPECiQUgvHbTPMVgsCIe9F0qbDQ7p79gWeJzY6nmI=; b=ursapuuJIltlUxy1X7oJJKNKRukpATVlRxgu9Z5mBzYUxHabxWUXZyxua286CzgJnz Or0N8Kz0mmPPF36eZGNbx/IXgeT1ZPH/CL20CVFGcs21bS892SaHB5VxEswqV//e1bd7 aU777pHAaTONfBr4HZxkumpRwEZ+Tfl/c3NAXKWjHlC9u5S5ZzVSOtIJGRng9OJg7q+1 2GHOLIK3l5D5fmqB3aqFApKC1s552QppnM0juS7vwD3wVRjFO1OsHfaGjHUbBLa52BIH bFFg6IjXsgw0yJhnSqGefJRpaPHZYwhZ4XBbj7NZB/ZOVZ9/QTgDVBiZPbdr15u0Xs96 pzlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:user-agent :mime-version; bh=oVvPECiQUgvHbTPMVgsCIe9F0qbDQ7p79gWeJzY6nmI=; b=PZ4BVd7qfbC8VRebSWBXIKV8bDtkbJrNM9XeIII3FtN867b7DqvtiUodRJpH0CJOoA ilpYdXGEs1hvizevxAYIjrmPBykq418fj7+SsqKHw8ZYjVjI8mevEcbH1N1cZEVdtPAs pQ7GctzDWCE0gWLmlHWLHmc7Nri/3b4VRaL67Avp26DwcIK1NhoAT5Rw/5xeNgHKeeuf eaTWAvlPIbRw9/B4zifFNxwiu8k76G001uBUtbH5QHI2mvp+2EZMq4TEyawEnbOlkxXL dkzJxq2gyfjACjCnw8vI0R3Q1g2+UJqiD9QiLtePGbitqzSiBFwACzUjN1yh4TzZD9Ru NVkw== X-Gm-Message-State: AMke39nl89Jq02XJwS/yYHM1Tc66zkM9F/QX/ABrt+lEtqDv30rLpMpoAt4zn2qROcjykg== X-Received: by 10.200.53.50 with SMTP id y47mr22078866qtb.114.1487011392141; Mon, 13 Feb 2017 10:43:12 -0800 (PST) Received: from [192.168.245.27] ([65.183.149.206]) by smtp.gmail.com with ESMTPSA id r24sm8034443qkl.5.2017.02.13.10.43.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 10:43:11 -0800 (PST) Date: Mon, 13 Feb 2017 13:43:10 -0500 (EST) From: Steven Hirsch X-X-Sender: hirsch@z87 To: pgsql-admin@postgresql.org Subject: Cannot drop role Message-ID: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org I've seen one or two mentions of this problem with no applicable solution. I have a case where I cannot drop a role because "...5 objects depend on it" (according to pgAdmin 3). When I connect to the database that holds those objects (they are not named) and try to drop the role I get an error message: [Error Code: 0, SQL State: XX000] ERROR: could not find tuple for default ACL 2243075 Even after trying a number of queries that are purported to list grants and ownerships for given ids I can turn up nothing that references the role by name. At this point I suspect there's something corrupted in the system catalog. How can I find the table entry (or entries) that reference that identifier? The fact that the message is issued suggests a link somewhere but I cannot locate it. Many thanks! Steve -- -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin