Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bUgJk-0007Vt-U5 for pgsql-admin@arkaria.postgresql.org; Tue, 02 Aug 2016 20:29:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bUgJk-0005V8-Co for pgsql-admin@arkaria.postgresql.org; Tue, 02 Aug 2016 20:29:36 +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 1bUgI1-0000FW-Tw for pgsql-admin@postgresql.org; Tue, 02 Aug 2016 20:27:50 +0000 Received: from mail-wm0-x230.google.com ([2a00:1450:400c:c09::230]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bUgHz-0002Di-6n for pgsql-admin@postgresql.org; Tue, 02 Aug 2016 20:27:49 +0000 Received: by mail-wm0-x230.google.com with SMTP id i5so306843107wmg.0 for ; Tue, 02 Aug 2016 13:27:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flexibee-eu.20150623.gappssmtp.com; s=20150623; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=4Edw5jBtwyKHVVDBEPQ/bdNt0TOxq5Ss3jhLWqzYdw4=; b=bcM8qKNM4FLGTx/sMGOn4H26I+1HC/OtK5+UtX5f0b1LxU8bl5Ansr1Flmj5ZvWd7j URfcc9xTCDNnGxyDQh1AiotR7HQErojNu+LgGtNzAqSWtT7AGZJEn8hrdxoNUTU0yZSh TEs6GgmPUlzfkR2yWOoFTCXkA8c6jhUtw+dVNawmxKxpbS5GeJ0r/Y5y9nr/c0/AiS8x 9VgIHY+/NGd9FzwW+j6d/RcP85XU23hLZVh/+JIgztUJCwF1ZxjP19XwprF7k8ihTWV7 4oKqk+wxaWjqptomNkgVB3Kj8aspivdbcuti/7OM4rr2xpgwoX5eBWlCJubXnR5bwX1C SWSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=4Edw5jBtwyKHVVDBEPQ/bdNt0TOxq5Ss3jhLWqzYdw4=; b=AHFj9ZhOJ9pmSQ32SuX0GrITnRm6rkeeC7ow9B9Trx4stN7kWMwj0CZj4wiWs75nGt wVsxPu55UIWnMufSDM90RbBPaaeathTBlSxlAD8cQkTp9Hte8ngybt7l8OnRhGJhTZTF 1kV4+PsU0FtWRsB9Zt9ZLPr61lsF5JLxsWKwN5jpho/edIVUr3DkCaUe/iSz0AzZ/v4f /3FZVPzct45M6skzyjut0Vb7/r6V/77VLZkCJB5+5HAXWjzDg6FH3T/+jwVviPf4Mkzj WYqmT5EIB73eN8WdFyCr2aP8ilAdIJzg3wS34Kn7HrRsWuxW/+HiwRGacvkiq60D7zTe vnnQ== X-Gm-Message-State: AEkoous7hjDUbmCkc1SkVXAChaD9eghAMQwz9GA89xK1IRTGClLh+P+fFzjtLdoL4AOhAtrz X-Received: by 10.194.97.73 with SMTP id dy9mr58326881wjb.132.1470169664753; Tue, 02 Aug 2016 13:27:44 -0700 (PDT) Received: from osvetlik.home ([77.48.30.240]) by smtp.gmail.com with ESMTPSA id n6sm4254260wjj.5.2016.08.02.13.27.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 13:27:44 -0700 (PDT) From: =?UTF-8?B?T25kxZllaiBTdsSbdGzDrWs=?= Subject: Re: Revoke delete on a table for super user To: pgsql-admin@postgresql.org References: <18971.1470158828@sss.pgh.pa.us> Message-ID: <997e138a-f05d-4f30-3bcc-85459ef7c898@flexibee.eu> Date: Tue, 2 Aug 2016 22:27:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <18971.1470158828@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) 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 Dne 2.8.2016 v 19:27 Tom Lane napsal(a): > "Campbell, Lance" writes: >> Is there a way to revoke the ability to perform delete on a table for a user that is a super user? > > No. Superusers bypass all access controls, by definition. Your best bet > is to not do more than you absolutely must as a superuser. > > regards, tom lane > > I guess you could achieve this using a trigger. Regards, Ondřej -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin