On 05/25/2016 03:37 AM, Tom Lane wrote:
Andreas Karlsson <andr...@proxel.se> writes:
Ok, then I can avoid touching all functions which are only called by
operator classes, tsearch, pls, fdws, etc. Which also means that there
is no need to care about Tom's changes to the signatures of GIN and GiST
support functions.
I think as long as you already did the work, we should keep those updates.
I'm not totally convinced by Alexander's argument that those changes pose
a future hazard, but I'm not convinced he's wrong either. If we're going
to be bumping a lot of contrib module versions anyway, it'd be silly to
take the risk that that's not a problem.
So how to best change the function signatures? I do not think it is
possible without locking indexes by just using the SQL commands. You
cannot drop a function from the operator family without dropping the
operator class first.
Is the correct solution to manually update pg_amop with a new value for
amopmethod?
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
