Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e3l8m-0000RQ-G3 for pgsql-admin@arkaria.postgresql.org; Sun, 15 Oct 2017 15:47:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e3l8l-0001W7-B5 for pgsql-admin@arkaria.postgresql.org; Sun, 15 Oct 2017 15:47:47 +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.84_2) (envelope-from ) id 1e3l8k-0001Ve-JV for pgsql-admin@postgresql.org; Sun, 15 Oct 2017 15:47:46 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e3l8h-00025S-Jj for pgsql-admin@postgresql.org; Sun, 15 Oct 2017 15:47:45 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v9FFlfj1019743; Sun, 15 Oct 2017 11:47:41 -0400 From: Tom Lane To: Karl Denninger cc: pgsql-admin@postgresql.org Subject: Re: Tsearch2 removal bit me - how to correct? In-reply-to: <64d687df-3a87-0e4a-e954-f2f23c2581c9@denninger.net> References: <64d687df-3a87-0e4a-e954-f2f23c2581c9@denninger.net> Comments: In-reply-to Karl Denninger message dated "Sun, 15 Oct 2017 10:37:04 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <19741.1508082461.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sun, 15 Oct 2017 11:47:41 -0400 Message-ID: <19742.1508082461@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Karl Denninger 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 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin