postgres/contrib/dict_int/dict_int.control

# dict_int extension
comment = 'text search dictionary template for integers'
default_version = '1.0'
module_pathname = '$libdir/dict_int'
relocatable = true
trusted = true
Convert contrib modules to use the extension facility. This isn't fully tested as yet, in particular I'm not sure that the "foo--unpackaged--1.0.sql" scripts are OK. But it's time to get some buildfarm cycles on it. sepgsql is not converted to an extension, mainly because it seems to require a very nonstandard installation process. Dimitri Fontaine and Tom Lane 2011-02-13 20:06:41 -05:00			`# dict_int extension`
			`comment = 'text search dictionary template for integers'`
			`default_version = '1.0'`
			`module_pathname = '$libdir/dict_int'`
			`relocatable = true`
Mark some contrib modules as "trusted". This allows these modules to be installed into a database without superuser privileges (assuming that the DBA or sysadmin has installed the module's files in the expected place). You only need CREATE privilege on the current database, which by default would be available to the database owner. The following modules are marked trusted: btree_gin btree_gist citext cube dict_int earthdistance fuzzystrmatch hstore hstore_plperl intarray isn jsonb_plperl lo ltree pg_trgm pgcrypto seg tablefunc tcn tsm_system_rows tsm_system_time unaccent uuid-ossp In the future we might mark some more modules trusted, but there seems to be no debate about these, and on the whole it seems wise to be conservative with use of this feature to start out with. Discussion: https://postgr.es/m/32315.1580326876@sss.pgh.pa.us 2020-02-13 15:02:35 -05:00			`trusted = true`