BUG #14860: pg_read_all_stats and pg_stat_replication

From: mdevan(dot)r(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Cc: mdevan(dot)r(at)gmail(dot)com
Subject: BUG #14860: pg_read_all_stats and pg_stat_replication
Date: 2017-10-18 12:40:22
Message-ID: 20171018124022.8210.3570@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14860
Logged by: Mahadevan R
Email address: mdevan(dot)r(at)gmail(dot)com
PostgreSQL version: 10.0
Operating system: any
Description:

User with pg_read_all_stats privilege is not able to read
some columns (listed below) from the pg_stat_replication
view. This is because these columns come from the function
pg_stat_get_wal_senders(), and this function returns non-null
values only for superuser.

To reproduce, set up streaming replication, and a user with
pg_read_all_stats privilege and "select * from
pg_stat_replication". The following columns will be null:

state
sent_lsn
write_lsn
flush_lsn
replay_lsn
sync_priority
sync_state

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-10-18 15:04:00 Re: Improper const-evaluation of HAVING with grouping sets and subquery pullup
Previous Message Mahadevan R 2017-10-18 12:16:07 pg_read_all_stats and pg_stat_replication in postgres 10.