Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-22 Thread Les
> > > I'm not sure what applied="public.pg", error="setting could not be > applied" > > means. > > No, "applied" is "f" (false), meaning that the setting is not actually > usable. > I'm a little surprised that it seems to have gotten into your live session > anyway, although perhaps that's because

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-21 Thread Tom Lane
Les writes: > mydatabase=# select * from pg_file_settings where name = > 'default_text_search_config'; > sourcefile | sourceline | seqno | >name| setting | applied |error > +-

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-21 Thread Les
> > 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_tex

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-21 Thread Tom Lane
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 sho

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-21 Thread Les
>> > SQL Error [22023]: ERROR: invalid value for parameter >> > "default_text_search_config": "public.pg " >> >Where: while setting parameter "default_text_search_config" to >> > "public.pg " parallel worker >> >> What client are you using to run the commands

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-21 Thread Les
> > > > SQL Error [22023]: ERROR: invalid value for parameter > > "default_text_search_config": "public.pg " > >Where: while setting parameter "default_text_search_config" to > > "public.pg " parallel worker > > What client are you using to run the commands?

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-21 Thread Adrian Klaver
On 7/21/23 08:14, Les wrote: Please reply to list also. Ccing list to get reply back on list. First I got this error when using a custom python program with asyncpg driver. https://magicstack.github.io/asyncpg/current/ Then I tried the "CREATE

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-21 Thread Adrian Klaver
On 7/20/23 22:25, Les wrote: I try to execute this on a very simple table, in a production database: alter table product.product add proc_order int8; create index idx_product_proc_order_status on product.product(proc_order nulls last, product_status_id /* this has type uuid */ ); and I get th

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-20 Thread Les
Version: PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit Extensions installed: oid |extname |extowner|extnamespace|extrelocatable|extversion|extconfig|extcondition| -++++--+--

Re: invalid value for parameter "default_text_search_config": "public.pg"

2023-07-20 Thread David G. Johnston
On Thursday, July 20, 2023, Les wrote: > I try to execute this on a very simple table, in a production database: > Please provide version information and any extensions you may have installed. David J.