From 749a787c5b25ae33b3d4da0ef12aa05214aa73c7 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 9 Jun 2016 16:44:25 -0400 Subject: Handle contrib's GIN/GIST support function signature changes honestly. In commits 9ff60273e35cad6e and dbe2328959e12701 I (tgl) fixed the signatures of a bunch of contrib's GIN and GIST support functions so that they would pass validation by the recently-added amvalidate functions. The backend does not actually consult or check those signatures otherwise, so I figured this was basically cosmetic and did not require an extension version bump. However, Alexander Korotkov pointed out that that would leave us in a pretty messy situation if we ever wanted to redefine those functions later, because there wouldn't be a unique way to name them. Since we're going to be bumping these extensions' versions anyway for parallel-query cleanups, let's take care of this now. Andreas Karlsson, adjusted for more search-path-safety by me --- contrib/btree_gist/btree_gist.control | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'contrib/btree_gist/btree_gist.control') diff --git a/contrib/btree_gist/btree_gist.control b/contrib/btree_gist/btree_gist.control index c7adfeb358c..74d0e92591f 100644 --- a/contrib/btree_gist/btree_gist.control +++ b/contrib/btree_gist/btree_gist.control @@ -1,5 +1,5 @@ # btree_gist extension comment = 'support for indexing common datatypes in GiST' -default_version = '1.1' +default_version = '1.2' module_pathname = '$libdir/btree_gist' relocatable = true -- cgit v1.2.3