From: Tom Lane <tgl@sss.pgh.pa.us>
To: Karl Denninger <karl@denninger.net>
cc: pgsql-admin@postgresql.org
Subject: Re: Tsearch2 removal bit me - how to correct?
In-reply-to: <df3608d7-fa54-4ce1-0ff8-9e563e8ee61a@denninger.net>
References: <64d687df-3a87-0e4a-e954-f2f23c2581c9@denninger.net>
 <19742.1508082461@sss.pgh.pa.us>
 <25ef2548-e569-ba17-5902-5676f8fc62db@denninger.net>
 <28488.1508109913@sss.pgh.pa.us>
 <999bacf8-512d-6014-74ba-07ef5e3edf0a@denninger.net>
 <df3608d7-fa54-4ce1-0ff8-9e563e8ee61a@denninger.net>
Comments: In-reply-to Karl Denninger <karl@denninger.net>
	message dated "Sun, 15 Oct 2017 18:55:22 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2632.1508120335.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Sun, 15 Oct 2017 22:18:55 -0400
Message-ID: <2633.1508120335@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Karl Denninger <karl@denninger.net> writes:
> One more question - for safety do I also need to drop all the other
> previously-declared public functions such as rank*() (in all its forms)
> and concat even thought they do not reference the shared library, or are
> they safe to leave there?  I see there are pg_catalog copies of these as
> well....

I dunno about safety offhand, but I'd definitely make an effort to get
rid of them --- at minimum, you're risking confusion by leaving them
around.  All of the modern text search support functions are in
pg_catalog.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin