postgresql/contrib/hstore/hstore.control

# hstore extension
comment = 'data type for storing sets of (key, value) pairs'
default_version = '1.6'
module_pathname = '$libdir/hstore'
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 02:06:41 +01:00			`# hstore extension`
Bring hstore's comment into line with style of other contrib comments. All the other ones that are primarily a new datatype say "data type for <purpose>", so make this one similar. 2011-02-15 20:21:45 +01:00			`comment = 'data type for storing sets of (key, value) pairs'`
Add a 64-bit hash function for type hstore. There's some question about the correctness of the hash function, but if it's wrong, the 32-bit version is also wrong. Amul Sul, reviewed by Hironobu Suzuki Discussion: https://postgr.es/m/CAAJ_b947JjnNr9Cp45iNjSqKf6PA5mCTmKsRwPjows93YwQrmw@mail.gmail.com 2018-11-23 19:37:34 +01:00			`default_version = '1.6'`
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 02:06:41 +01:00			`module_pathname = '$libdir/hstore'`
			`relocatable = true`