| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FPW compression leaks information |
| Date: | 2015-04-09 16:07:39 |
| Message-ID: | 20150409160739.GC3663@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Heikki Linnakangas (hlinnaka(at)iki(dot)fi) wrote:
> On 04/09/2015 06:28 PM, Stephen Frost wrote:
> >* Heikki Linnakangas (hlinnaka(at)iki(dot)fi) wrote:
> >>What should we do about this? Make it configurable on a per-table
> >>basis? Disable FPW compression on system tables? Disable FPW on
> >>tables you don't have SELECT access to? Add a warning to the docs?
> >
> >REVOKE EXECUTE ON FUNCTION pg_current_xlog_insert_location() FROM public;
>
> Yeah, that's one option. Will also have to revoke access to
> pg_stat_replication and anything else that might indirectly give
> away the current WAL position.
Sure, though pg_stat_replication already only returns the PID and no
details, unless you're a superuser.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-04-09 16:14:19 | Re: deparsing utility commands |
| Previous Message | Heikki Linnakangas | 2015-04-09 16:05:00 | Re: FPW compression leaks information |