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 1qMvrB-003dTW-G9 for pgsql-general@arkaria.postgresql.org; Fri, 21 Jul 2023 19:32:05 +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 1qMvr8-0073RR-MB for pgsql-general@arkaria.postgresql.org; Fri, 21 Jul 2023 19:32:02 +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 1qMvr8-0073MR-BQ for pgsql-general@lists.postgresql.org; Fri, 21 Jul 2023 19:32:02 +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 1qMvr2-000z9D-Oa for pgsql-general@lists.postgresql.org; Fri, 21 Jul 2023 19:32:00 +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 36LJVrYJ983598; Fri, 21 Jul 2023 15:31:53 -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> Comments: In-reply-to Les message dated "Fri, 21 Jul 2023 20:59:08 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <983596.1689967913.1@sss.pgh.pa.us> Date: Fri, 21 Jul 2023 15:31:53 -0400 Message-ID: <983597.1689967913@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Les writes: > I found out that "public.pg" is not a valid configuration indeed. Quite so (and even more so given that the actual setting seems to be "public.pg "). > But I still don't know how it affects a query that does not use any > tsvector or tsquery. The error report shows that the failure is happening while starting a parallel worker, so the only thing required of your query is that it be big enough to tempt the planner to use parallelism. However, the parallel worker should just be absorbing the same configuration settings your main session is using. So what remains to be explained is why you aren't seeing the same complaint when starting a fresh session. It might be useful to look at the output of show default_text_search_config; and select * from pg_file_settings where name = 'default_text_search_config'; regards, tom lane