postgresql/contrib/pg_visibility/pg_visibility.control

# pg_visibility extension
comment = 'examine the visibility map (VM) and page-level visibility info'
default_version = '1.2'
module_pathname = '$libdir/pg_visibility'
relocatable = true
Add pg_visibility contrib module. This lets you examine the visibility map as well as page-level visibility information. I initially wrote it as a debugging aid, but was encouraged to polish it for commit. Patch by me, reviewed by Masahiko Sawada. Discussion: 56D77803.6080503@BlueTreble.com 2016-03-08 21:38:50 +08:00			`# pg_visibility extension`
			`comment = 'examine the visibility map (VM) and page-level visibility info'`
Default monitoring roles Three nologin roles with non-overlapping privs are created by default * pg_read_all_settings - read all GUCs. * pg_read_all_stats - pg_stat_, pg_database_size(), pg_tablespace_size() pg_stat_scan_tables - may lock/scan tables Top level role - pg_monitor includes all of the above by default, plus others Author: Dave Page Reviewed-by: Stephen Frost, Robert Haas, Peter Eisentraut, Simon Riggs 2017-03-31 02:18:53 +08:00			`default_version = '1.2'`
Add pg_visibility contrib module. This lets you examine the visibility map as well as page-level visibility information. I initially wrote it as a debugging aid, but was encouraged to polish it for commit. Patch by me, reviewed by Masahiko Sawada. Discussion: 56D77803.6080503@BlueTreble.com 2016-03-08 21:38:50 +08:00			`module_pathname = '$libdir/pg_visibility'`
			`relocatable = true`