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 14:49:59 -0500
Message-ID: <25ef2548-e569-ba17-5902-5676f8fc62db@denninger.net> (raw)
In-Reply-To: <19742.1508082461@sss.pgh.pa.us>
References: <64d687df-3a87-0e4a-e954-f2f23c2581c9@denninger.net>
	<19742.1508082461@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On 10/15/2017 10:47, Tom Lane wrote:
> Karl Denninger <karl@denninger.net> writes:
>> Attempting to migrate to 10.0 from 9.6, which has had "tsearch2" loaded
>> for backward compatibility since "forever" (which I suspect is no longer
>> really required as the capability is internal and has been for a long
>> time) results in this blowup logged in loadable_libraries.txt:
>> could not load library "$libdir/tsearch2": ERROR:  could not access file
>> "$libdir/tsearch2": No such file or directory
>> So what's causing this to be requested on startup and how do I kill it? 
> Look for '$libdir/tsearch2' in the pg_proc.probin column of each
> DB in the installation ...
>
> 			regards, tom lane
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)

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)

fapforum=# drop function prsd_end(internal);
ERROR:  cannot drop function prsd_end(internal) because it is required
by the database system

The others I can drop, but I wind up with these in each database... any
idea where the piece is that the original package stuffed in that I need
to get rid of so I can kill these?

-- 
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: <25ef2548-e569-ba17-5902-5676f8fc62db@denninger.net>
Permalink:  ../25ef2548-e569-ba17-5902-5676f8fc62db@denninger.net/
Also on:    postgresql.org/message-id/25ef2548-e569-ba17-5902-5676f8fc62db@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: <25ef2548-e569-ba17-5902-5676f8fc62db@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