postgres/contrib/dblink/dblink.control

# dblink extension
comment = 'connect to other PostgreSQL databases from within a database'
default_version = '1.2'
module_pathname = '$libdir/dblink'
relocatable = 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-14 04:06:41 +03:00			`# dblink extension`
			`comment = 'connect to other PostgreSQL databases from within a database'`
Update dblink extension for parallel query. Almost all functions provided by this extension are PARALLEL RESTRICTED. Mostly, that's because the leader's TCP connections won't be shared with the workers, but in some cases like dblink_get_pkey it's because they obtain locks which might be released early if taken within a parallel worker. dblink_fdw_validator probably can't be used in a query anyway, but there would be no problem from the point of view of parallel query if it were, so it's PARALLEL SAFE. Andreas Karlsson 2016-06-17 22:09:57 +03:00			`default_version = '1.2'`
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-14 04:06:41 +03:00			`module_pathname = '$libdir/dblink'`
			`relocatable = true`