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

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"

> > 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"

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"

>> > 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"

> > > > 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"

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: aclitem binary encoding

Joseph Koshakow writes: > Is this an intentional decision to not support a binary encoding for > aclitem types? Or is it just a lack of a feature? I think it's at least somewhat intentional, to have a core type that has no binary I/O so that that case can be tested. In any event, a binary repres

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

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

aclitem binary encoding

Hi all, I was using a PostgreSQL driver that used binary input/output to query some ACL data and was surprised to see the following error: no binary output function available for type aclitem In fact, aclitem has no binary input or output functions postgres=# SELECT typinput, typoutput,

Re: Moving data from huge table slow, min() query on indexed column taking 38s

On Thu, 6 Jul 2023, Dimitrios Apostolou wrote: + Then I broke the command above in many small chunks WITH rows AS ( DELETE FROM tbl_legacy AS t WHERE (partition_key_column < $1) RETURNING t.* ) INSERT INTO tbl SELECT * FROM rows; CO