From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: WAL's listing in pg_xlog by some sql query |
Date: | 2016-06-03 02:32:02 |
Message-ID: | CAB7nPqTns4VkpFq62wVWeu8AYqGyqLD_nd=NstbOrL4cUpjgBg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jun 3, 2016 at 11:23 AM, Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> wrote:
>
>
> On Fri, Jun 3, 2016 at 4:30 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>>
>> * Sameer Kumar (sameer(dot)kumar(at)ashnik(dot)com) wrote:
>> > On Fri, 3 Jun 2016, 12:14 a.m. Alex Ignatov, <a(dot)ignatov(at)postgrespro(dot)ru>
>> > wrote:
>> > > Can I list all WAL files in pg_xlog by using some sql query in
>> > > Postgres?
>> >
>> > Try
>> >
>> > Select pg_ls_dir('pg_xlog');
>>
>> Note that this currently requires superuser privileges.
>>
>> Given the usefulness of this specific query and that it could be used
>> without risk of the user being able to gain superuser access through it,
>> I'd like to see a new function added which does not have the superuser
>> check, but is not allowed to be called by public initially either.
>
>
> Can I not wrap it around another user defined function with SECURITY DEFINER
> and grant privilege to specific users who can use it?
pg_ls_dir() has a check on superuser() embedded in its code.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Baker | 2016-06-03 03:37:16 | Re: PL/PGSQL + inserts+updates+limit - Postgres 9.3 |
Previous Message | Patrick Baker | 2016-06-03 02:29:40 | Re: PL/PGSQL + inserts+updates+limit - Postgres 9.3 |