>> > SQL Error [22023]: ERROR: invalid value for parameter >> > "default_text_search_config": "public.pg <http://public.pg>" >> > Where: while setting parameter "default_text_search_config" to >> > "public.pg <http://public.pg>" parallel worker >> >> What client are you using to run the commands? >> >> I just checked and it also throws this error when I execute the following >> SELECT from plain psql: > > > select > pft.id as file_type_id, > pft.code as file_type_code, > pfs.id as file_status_id, > pfs.code as file_status_code, > count(pf.id) as cnt > from > product.product_file pf > inner join product.product p on p.id=pf.product_id > > inner join product.product_file_type pft on > pft.id = pf.product_file_type_id > inner join product.product_file_status pfs on > pfs.id = pf.product_file_status_id > group by > pft.id, pfs.id; > ERROR: invalid value for parameter "default_text_search_config": " > public.pg" > CONTEXT: while setting parameter "default_text_search_config" to " > public.pg" > parallel worker > > After reading the documentation here:
https://www.postgresql.org/docs/current/textsearch-configuration.html I found out that "public.pg" is not a valid configuration indeed. Here is how it looks in this db: mydatabase=# mydatabase=# \dF List of text search configurations Schema | Name | Description ------------+------------+--------------------------------------- pg_catalog | arabic | configuration for arabic language pg_catalog | armenian | configuration for armenian language pg_catalog | basque | configuration for basque language pg_catalog | catalan | configuration for catalan language pg_catalog | danish | configuration for danish language pg_catalog | dutch | configuration for dutch language pg_catalog | english | configuration for english language pg_catalog | finnish | configuration for finnish language pg_catalog | french | configuration for french language pg_catalog | german | configuration for german language pg_catalog | greek | configuration for greek language pg_catalog | hindi | configuration for hindi language pg_catalog | hungarian | configuration for hungarian language pg_catalog | indonesian | configuration for indonesian language pg_catalog | irish | configuration for irish language pg_catalog | italian | configuration for italian language pg_catalog | lithuanian | configuration for lithuanian language pg_catalog | nepali | configuration for nepali language pg_catalog | norwegian | configuration for norwegian language pg_catalog | portuguese | configuration for portuguese language pg_catalog | romanian | configuration for romanian language pg_catalog | russian | configuration for russian language pg_catalog | serbian | configuration for serbian language pg_catalog | simple | simple configuration pg_catalog | spanish | configuration for spanish language pg_catalog | swedish | configuration for swedish language pg_catalog | tamil | configuration for tamil language pg_catalog | turkish | configuration for turkish language pg_catalog | yiddish | configuration for yiddish language (29 rows) mydatabase=# SET default_text_search_config = 'pg_catalog.english'; SET mydatabase=# After setting it to pg_catalog.english, it works. But I still don't know how it affects a query that does not use any tsvector or tsquery. In fact, tsvector and tsquery types are not used in any of my tables at all. > >
