diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-06-09 16:44:25 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-06-09 16:44:25 -0400 |
| commit | 749a787c5b25ae33b3d4da0ef12aa05214aa73c7 (patch) | |
| tree | df8675f8f950e306a9deb1af6b85352c08ba422c /src/backend/parser/parse_utilcmd.c | |
| parent | b12fd41c695b43c76b0a9a4d19ba43b05536440c (diff) | |
| download | postgresql-749a787c5b25ae33b3d4da0ef12aa05214aa73c7.tar.gz postgresql-749a787c5b25ae33b3d4da0ef12aa05214aa73c7.zip | |
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
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions