pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karl Denninger <karl@denninger.net>
To: pgsql-admin@postgresql.org
Subject: Re: Tsearch2 removal bit me - how to correct?
Date: Sun, 15 Oct 2017 18:55:22 -0500
Message-ID: <df3608d7-fa54-4ce1-0ff8-9e563e8ee61a@denninger.net> (raw)
In-Reply-To: <999bacf8-512d-6014-74ba-07ef5e3edf0a@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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On 10/15/2017 18:42, Karl Denninger wrote:
> On 10/15/2017 18:25, Tom Lane wrote:
>> Karl Denninger <karl@denninger.net> writes:
>>> That worked on one of my clusters, but on another I'm seeing entries in
>>> pg_catalog, and can't remove them.
>>> pgsql=# \c fapforum
>>> You are now connected to database "fapforum" as user "pgsql".
>>> fapforum=# select proname from pg_proc where probin like '%tsearch2%';
>>>     proname
>>> ----------------
>>>  prsd_end
>>>  prsd_lextype
>>>  prsd_start
>>>  thesaurus_init
>>> (4 rows)
>> There *should* be a pg_catalog.prsd_end built-in function, but it's
>> going to have null probin.  I think you're being careless about
>> schema names here.
>>
>>> fapforum=# \df prsd_end;
>>>                             List of functions
>>>    Schema   |   Name   | Result data type | Argument data types |  Type
>>> ------------+----------+------------------+---------------------+--------
>>>  pg_catalog | prsd_end | void             | internal            | normal
>>> (1 row)
>> This does not prove that there's not a, say, public.prsd_end.  Try
>> "\df *.prsd_end" to see all the functions by that name.
>>
>> 			regards, tom lane
> You are correct.  Thanks; got it.  (That's what I get for not being
> specific)
>
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....

-- 
Karl Denninger
karl@denninger.net <mailto:karl@denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/

Attachments:

  smime.p7s (application/pkcs7-signature, 4.8K) download

view thread (13+ messages)  latest in thread

Message-ID: <df3608d7-fa54-4ce1-0ff8-9e563e8ee61a@denninger.net>
Permalink:  ../df3608d7-fa54-4ce1-0ff8-9e563e8ee61a@denninger.net/
Also on:    postgresql.org/message-id/df3608d7-fa54-4ce1-0ff8-9e563e8ee61a@denninger.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: karl@denninger.net
  Subject: Re: Tsearch2 removal bit me - how to correct?
  In-Reply-To: <df3608d7-fa54-4ce1-0ff8-9e563e8ee61a@denninger.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox