Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1Dki-0003M8-4R for pgsql-admin@arkaria.postgresql.org; Wed, 28 Mar 2018 16:16:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f1Dkg-0007kq-Ek for pgsql-admin@arkaria.postgresql.org; Wed, 28 Mar 2018 16:16:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1Dkg-0007ka-1c for pgsql-admin@lists.postgresql.org; Wed, 28 Mar 2018 16:16:42 +0000 Received: from mail-oi0-x244.google.com ([2607:f8b0:4003:c06::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1f1Dkd-0001EF-KT for pgsql-admin@lists.postgresql.org; Wed, 28 Mar 2018 16:16:40 +0000 Received: by mail-oi0-x244.google.com with SMTP id e8-v6so2624045oii.4 for ; Wed, 28 Mar 2018 09:16:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=S5QwBYBinQs1GEaSF1Kz2+aT6xH6JuJxkeAULfWarpA=; b=YYaBpGuybIsRT4UyHdqyVBZWL5eZiCidu6098SCA14IKGWZtMin5b3SDfdBZf29Kag nG190eGgAhg6ruOTAKc/YzCpDjy1A1Om2xMSlSzSIKFR67EfzANE6tLiW3astRH23RJF IyLIO0d8Aala7t9kDTVOeHuzf1gK663FJWDZCnPl3aS8gHJ2QG4R+K/wQ/PAdMpdkk4c 7fVi+KEcI0fI4nzZGxJsmAhtGoKSTosP/nCuft5Ue+rAZZKDqaeCZzj/H6O2gfw7PKRn dwmLsklxTHVOyjfd8NmdpRYkdv6os46QHCaGoPrqPBUZTf4/5cOYuD9U0torZX2+/n6i OAhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=S5QwBYBinQs1GEaSF1Kz2+aT6xH6JuJxkeAULfWarpA=; b=F1sV+XAfIjUieCrOG/p1h0uuhMhx3LrF6iedLDMnnMSI9Fc7E5iCaa6nNFInkUR6gP wIH9AMfOhf+qEbM+zObeZKSDDK1o2xNLdxqK37DSmjNr+W02Zxws3ZLjA8TYKZmnXxbB 4ZDbe/pWofngFjlShuNZwJklcI6Pjg2IdCvtI91i4N8vCC/xqQy/fPT3cehAkqc6zgdE 71I+0O1nom8piKqmv/NQV21nY97zKn4ZXyuK9eDuRwECYD9QjHe72LRzDQ7KT8Ytkrdd NluigOx7BErJuMr4mnL0L+hgJM2sh/466Fj78XbCFCTGaR6tHYI0XLZ3ATwTBr10ilvi 7uvQ== X-Gm-Message-State: AElRT7Gm/A1dP99GcMxP7vZef/9aT91uAJSrBztxzkWVdodOix24yvcz XTw27XN1weH/sFPLHeeDZ5txamO5hfcc8EfY3ic= X-Google-Smtp-Source: AIpwx4/FLEEYCcZEed6puKUzSsLDw6OXQ40b7R5Su4z9MHbb08Sk2RBMNfWf7BhHuT/vYxL3EmPHJJgow07QiYPRcRA= X-Received: by 10.202.4.5 with SMTP id 5mr2470424oie.9.1522253798553; Wed, 28 Mar 2018 09:16:38 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:5f0d:0:0:0:0:0 with HTTP; Wed, 28 Mar 2018 09:15:58 -0700 (PDT) In-Reply-To: <27739.1522214819@sss.pgh.pa.us> References: <27739.1522214819@sss.pgh.pa.us> From: Wells Oliver Date: Wed, 28 Mar 2018 09:15:58 -0700 Message-ID: Subject: Re: postgres 9.6.8 to 10 on Ubuntu 16.04.4 LTS --- tsearch2 unloadable... To: Tom Lane Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="001a11c035daebbfdb05687b5472" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a11c035daebbfdb05687b5472 Content-Type: text/plain; charset="UTF-8" Thanks. I ran: select * from pg_proc where probin like '%tsearch%'; This showed 38 functions. I believe I need to drop these, correct? However, I am using to_tsvector() and to_tsquery(), but I believe these are now part of the core postgres package, and I can safely drop these where probin contains tsearch2. Am I correct, or do I need to rewrite things that use to_tsvector()? Thanks for any clarification. On Tue, Mar 27, 2018 at 10:26 PM, Tom Lane wrote: > Wells Oliver writes: > > I get that this library is no longer need. It's blowing up my upgrade to > > 10. Output: > > could not load library "$libdir/tsearch2": ERROR: could not access file > > "$libdir/tsearch2": No such file or directory > > > But I can't see how or where this library is still installed. Running \dx > > on my database: > > Did you check every database in the cluster? > > If you did, then maybe you have some "loose" (pre-extensions) tsearch2 > functions laying about somewhere. Look through pg_proc for functions > with probin = '$libdir/tsearch2'. Again, check every DB. > > regards, tom lane > -- Wells Oliver wells.oliver@gmail.com --001a11c035daebbfdb05687b5472 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks. I ran:=C2=A0select * from pg_proc where probin lik= e '%tsearch%';

This showed 38 functions. I belie= ve I need to drop these, correct? However, I am using to_tsvector() and to_= tsquery(), but I believe these are now part of the core postgres package, a= nd I can safely drop these where probin contains tsearch2. Am I correct, or= do I need to rewrite things that use to_tsvector()?

Thanks for any clarification.


<= div class=3D"gmail_extra">
On Tue, Mar 27, 20= 18 at 10:26 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Wells Oliver <wells.oliver@gmail.com> writes:
> I get that this library is no longer need. It's blowing up my upgr= ade to
> 10. Output:
> could not load library "$libdir/tsearch2&= quot;: ERROR:=C2=A0 could not access file
> "$libdir/tsearch2": No such file or directory

> But I can't see how or where this library is still installed. Runn= ing \dx
> on my database:

Did you check every database in the cluster?

If you did, then maybe you have some "loose" (pre-extensions) tse= arch2
functions laying about somewhere.=C2=A0 Look through pg_proc for functions<= br> with probin =3D '$libdir/tsearch2'.=C2=A0 Again, check every DB.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane



--
--001a11c035daebbfdb05687b5472--