Message-ID: <46009.192.168.207.54.1427812926.squirrel@webmail.etecsa.cu>
In-Reply-To: <20150331133130.GK3663@tamriel.snowman.net>
References: 
 <CAL0F7ned0Lbcu_FnzcoLTRS8zpQsmkA0fyw7jXOz9X=WHyJTYw@mail.gmail.com>
 <20150331131252.GI3663@tamriel.snowman.net>
 <45998.192.168.207.54.1427812184.squirrel@webmail.etecsa.cu>
 <20150331133130.GK3663@tamriel.snowman.net>
Date: Tue, 31 Mar 2015 09:42:06 -0500 (GMT+5)
Subject: Re: Permission select pg_stat_replication
From: "Gilberto Castillo" <gilberto.castillo@etecsa.cu>
To: "Stephen Frost" <sfrost@snowman.net>
Cc: "Gilberto Castillo" <gilberto.castillo@etecsa.cu>, jesse.waters@gmail.com,
 pgsql-admin@postgresql.org
Reply-To: gilberto.castillo@etecsa.cu
User-Agent: SquirrelMail/1.4.8-5.el5_4.10
MIME-Version: 1.0
Importance: Normal
Content-Type: multipart/mixed; boundary="=t8fP8KJn00818=imx3.etecsa.cu="
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

This is a multi-part message in MIME format.

--=t8fP8KJn00818=imx3.etecsa.cu=
Content-Disposition: inline
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit


> Gilberto,
>
> * Gilberto Castillo (gilberto.castillo@etecsa.cu) wrote:
>> > * jesse.waters@gmail.com (jesse.waters@gmail.com) wrote:
>> >>  Could someone tell me what permission is required to
>> >> select * from pg_stat_replication; ?
>> >
>> > Currently, you're required to have superuser rights.
>> >
>> >> I like to setup a monitor to query database with minimal privileges
>> >> necessary.
>> >
>> > I agree 110% and am actively working to fix exactly this issue.  I
>> hope
>> > to have a patch in the next day or so which will allow you to GRANT
>> > rights to such a monitor user which will allow that user to see all
>> the
>> > contents of pg_stat_replication.
>> >
>> > One thing which would be really great is if you have time to test with
>> > the patch I'm working up (it's against 9.5, but this is strictly
>> > functionality testing and should be just in in a dev/test environment,
>> > I wouldn't suggest running 9.5 in production, of course!).
> [...]
>> SET SESSION AUTHORIZATION postgres;
>>
>> GRANT SELECT ON pg_stat_replication TO usuario1;
>
> This is (essentially) what I'm hoping to enable.  Note that this won't
> do anything for you today as the view is already available to all users
> on the system and it's actually the function underneath which is
> filtering the result set.
>

Uhmmm,

ALTER DEFAULT PRIVILEGES FOR ROLE postgres GRANT SELECT ON VIEWS  TO
usuario1;

Nor does it work?

Saludos,
Gilberto Castillo
La Habana, Cuba

--=t8fP8KJn00818=imx3.etecsa.cu=
Content-Type: text/plain
Content-Disposition: inline

--- 
This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu
Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com>

--=t8fP8KJn00818=imx3.etecsa.cu=
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


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

--=t8fP8KJn00818=imx3.etecsa.cu=--