From: | Murat Efendioğlu <mrtdmrts001(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Error when setting default_text_search_config |
Date: | 2024-10-05 17:46:02 |
Message-ID: | CACbCzujQ4zS8MM1bx-==+tr+D3Hk5G1cjN4XkUQ+Q=cEpwhzqg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
*Hello everyone,*
I've encountered some strange behavior in the new PostgreSQL 17 version.
Previously, in versions before 17, I was able to set the
default_text_search_config like this:
sql
Copy code
ALTER DATABASE "MyDatabase" SET default_text_search_config TO 'german';
Everything worked fine. However, after upgrading to PostgreSQL 17, when I
ran the same ALTER statement on the new database, my database entered
recovery mode.
The solution was to update the statement as follows:
sql
Copy code
ALTER DATABASE "MyDatabase" SET default_text_search_config TO
'pg_catalog.german';
It turns out I had to prefix the language with pg_catalog to resolve the
issue.
Environment: Windows Server 2022 Standard 21H2 with PostgreSQL 17 installer
Best regards m.d.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-10-05 18:48:05 | Re: BUG #18637: CREATE INDEX won't look up operator classes in search_path if PARTITION BY is specified |
Previous Message | Amit Kapila | 2024-10-05 10:20:05 | Re: BUG #18641: Logical decoding of two-phase commit fails with TOASTed default values |