Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fmc8H-0007Ph-VO for pgsql-admin@arkaria.postgresql.org; Mon, 06 Aug 2018 09:48:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fmc8D-0003QB-TB for pgsql-admin@arkaria.postgresql.org; Mon, 06 Aug 2018 09:48:53 +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.89) (envelope-from ) id 1fmc8C-0003Pv-VW for pgsql-admin@lists.postgresql.org; Mon, 06 Aug 2018 09:48:53 +0000 Received: from nh602-vm3.bullet.mail.ssk.yahoo.co.jp ([182.22.90.28]) by magus.postgresql.org with smtp (Exim 4.89) (envelope-from ) id 1fmc85-00060Q-Hg for pgsql-admin@lists.postgresql.org; Mon, 06 Aug 2018 09:48:49 +0000 Received: from [182.22.66.105] by nh602.bullet.mail.ssk.yahoo.co.jp with NNFMP; 06 Aug 2018 09:48:39 -0000 Received: from [182.22.91.128] by t603.bullet.mail.ssk.yahoo.co.jp with NNFMP; 06 Aug 2018 09:48:39 -0000 Received: from [127.0.0.1] by omp601.mail.ssk.yahoo.co.jp with NNFMP; 06 Aug 2018 09:48:39 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 172085.29000.bm@omp601.mail.ssk.yahoo.co.jp Received: (qmail 66408 invoked by uid 60001); 6 Aug 2018 09:48:38 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1533548918; bh=td4mz2ourqJPQ7C0viQBbY96WtF+TsEosJnPlIPzRIE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=uupiD18ZkplungZivh0kFHLNEX1a6FMasxgTXymF8yWotCTW3ZdFa6Lk7DEcYDJPO4sTBoW6uQW31omZpoVKePbBiRhGCwxg2YgBaJhNuOsRnMVtO1zQlLlO6SCLyQ8DGBdBlxEfShnh95BRnhiMRnVrp7GHdoAMJesQ+u1bnmE= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=DVQTYyO8eESTXN38wtSRGuvtPKtvlSWmOqssCEeWq/Whn8It753qhBq+SmIyDgtedDRvpMnxIqqapcF7pBJTPHKrAkOFpsIdCitGUsez/59xOTFg9uoEaBiSUfFYNjbx2gdBZnqCF9uSNNzsiHelzLEa8qa3tmyz9yeQAEoFgj8=; Message-ID: <913907.28546.qm@web103014.mail.kks.yahoo.co.jp> X-YMail-OSG: Aik8fcMVM1mZZra3GVGohjVUwdC6yhyFd_1JVjmZCg4n5wReNxKaWSzhkLenLFubZAw0WN_B7.9PVYJ6ngWcTZTnq1GMGvw53ueFOctl5e6i3bOE1W5kaRzxAsojy6tu5g4BZ4_j7wEfjavkEmJEJSOWkU95IboAG4ULafG7LLNdnPxUg1z9xlcXVCQggDEbuqoAj0vtPxmduHi3m6H5ar6br3EgivkTmeCacfVlz3BrNu3NghrOshSXDmTLxUkIiyhQfSa7onQ5luJSFJCjmlNdL.TLASmsbhZxtkwuTJX5MrtQuidDLldcbg0vx7WnUUpHSZYGsS9brW1osvvwsN0M_k82Jh1E4hjoZNgjvF4a2vUl.vs_DnG1fdPJo16re19xdg1qdoz1eYO2.nLFfoXGk0sq0fL5Aem_MFahUWmSkWkWKGOJSDNmj7RNQQqUpD3RwJ7w_zObU28dwvwQpOlL7MP1Kx7dJ1XZO_QKlLkNWQW3Q0Qtv2SZpqIQZQFXgrmBJzrfXgLzjx2OuoKZ5oa.Y5VvfFcD5ZhY67rSWchHb52FJ1dpCnLEICoYj9QPd0wueslhK6Nbcem5I9A9LEATr363H3.Gh3ZcBTpkdac9y14f_KPZnEXYPYma6nY1dA-- Received: from [111.239.188.95] by web103014.mail.kks.yahoo.co.jp via HTTP; Mon, 06 Aug 2018 18:48:37 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: TvYzPfYVM1mCfimNtHGuW7898Qqdj267itctaFRN6SE8va7epwqC9DH1jr4e0aWRi7FzYFWUN3pouPwFKACBDNpDUVyhnoLwUXwoBfbydgL.G0GSmUUxAU_a0VZDxPGKOXRd Date: Mon, 6 Aug 2018 18:48:37 +0900 (JST) From: bejita0409@yahoo.co.jp Reply-To: bejita0409@yahoo.co.jp Subject: How to revoke privileged from PostgreSQL's superuser To: "pgsql-admin@lists.postgresql.org" , "pgsql-general@lists.postgresql.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-1144628612-454817048-1533548917=:28546" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ---1144628612-454817048-1533548917=:28546 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello,=0A=A0=0AI am a newbie DBA.=0A=A0=0AI have a request for revoking the= access to user's data from DBA-user.=0AI think the request is right becaus= e users should be the only ones can access their data.=0ABut DBA-user also = need full access to the other data? It means that DBA-user also needs to be= a superuser.=0A=A0=0ASo I conclude the request that how to revoke privileg= ed from superuser in postgres.=0A=A0=0AAs my knowledge, the superuser in Po= stgreSQL bypasses all the permission check.=0ASo that, there is no way to d= o it in PostgreSQL, is that right?=0A=A0=0AIs there some DBAs are faced wit= h this before?=0A=A0=0A=A0=0AThanks,=0A--=0Abejita ---1144628612-454817048-1533548917=:28546 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,
 
I am a newbie DBA.
 = ;
I have a request for revoking the acc= ess to user's data from DBA-user.
= I think the request is right because users should be the only ones can acce= ss their data.
But DBA-user also n= eed full access to the other data? It means that DBA-user also needs to be = a superuser.
 
So I conclude the request that how to revoke pri= vileged from superuser in postgres.
 
As my knowledge, the supe= ruser in PostgreSQL bypasses all the permission check.
So that, there is no way to do it in PostgreSQL, is that rig= ht?
 
Is there some DBAs are faced with this before?=
 
 
Thanks,
--
=0A= =0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A=0A= =0A=0A=0A=0A=0A=0A=0A=0A=0A=0A
bejita
---1144628612-454817048-1533548917=:28546--