On 04/09/2015 06:28 PM, Stephen Frost wrote:
* Heikki Linnakangas (hlinn...@iki.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.
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
