Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qMxNS-003gzc-7C for pgsql-general@arkaria.postgresql.org; Fri, 21 Jul 2023 21:09:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qMxNQ-008Psg-M3 for pgsql-general@arkaria.postgresql.org; Fri, 21 Jul 2023 21:09:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qMxNQ-008PsY-Au for pgsql-general@lists.postgresql.org; Fri, 21 Jul 2023 21:09:28 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qMxNI-00103s-HV for pgsql-general@lists.postgresql.org; Fri, 21 Jul 2023 21:09:27 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 36LL9FbG993881; Fri, 21 Jul 2023 17:09:15 -0400 From: Tom Lane To: Les cc: Adrian Klaver , pgsql-general@lists.postgresql.org Subject: Re: invalid value for parameter "default_text_search_config": "public.pg" In-reply-to: References: <61b544bf-32e1-2be8-eedc-4e2167fe7530@aklaver.com> <983597.1689967913@sss.pgh.pa.us> Comments: In-reply-to Les message dated "Fri, 21 Jul 2023 21:57:45 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <993879.1689973755.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 21 Jul 2023 17:09:15 -0400 Message-ID: <993880.1689973755@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Les writes: > mydatabase=3D# select * from pg_file_settings where name =3D > 'default_text_search_config'; > sourcefile | sourceline | seqno | > name | setting | applied | error > --------------------------------------------+------------+-------+------= ----------------------+-----------+---------+-----------------------------= - > /opt/postgresql/data/conf.d/06_locale.conf | 17 | 24 | > default_text_search_config | public.pg | f | setting could not be = applied > (1 row) > I'm not sure what applied=3D"public.pg", error=3D"setting could not be a= pplied" > means. No, "applied" is "f" (false), meaning that the setting is not actually usa= ble. I'm a little surprised that it seems to have gotten into your live session anyway, although perhaps that's because the postmaster can't really validate it at startup. > I can change it in the config file, no problem. I just would like to > know if this is a simple configuration error, or a software installation > error. (Is public.pg a built-in config that should always exist?) "public.pg" is certainly not a standard (as in built-in) text search configuration name. Maybe that value was installed by some bit of software that failed to install the configuration to go with it, or only put the configuration into one database not everywhere in your installation? regards, tom lane