Additional info:
The original schema was exported using pg_dump (whole db) and imported using "psql -f".
Then I've renamed the schema in PgAdmin(4.13) to "dev" (right click -> Properties -> change name -> Save).
If I rename back the schema to original name, and use that name in "currentSchema" param, then everything works correctly.
In addition, I don't know if any configuration may override the connection param "currentSchema" (such as hibernate overwriting "search_path"), but in my case it should be used as fallback to resolve missing text search configuration.
On Monday, September 30, 2019, 3:45:48 AM GMT+3, Dave Cramer <davecramer@gmail.com> wrote:
Interesting,
Thanks for the report.
The following bug has been logged on the website:
Bug reference: 16028
Logged by: cd a
Email address: cdalxndr@yahoo.com
PostgreSQL version: 10.3
Operating system: Windows 10
Description:
Using a java spring app with connection:
jdbc:postgresql://localhost:5433/postgres?currentSchema=dev,public&ApplicationName=myapp
Schema 'dev' has fts configuration 'en'.
Query (debugged PgPreparedStatement):
select * from dev.category where category.language='en'
the param 'en' is registered with oid (paramType) 3734 corresponding to
'regconfig' type
Query results in: ERROR: text search configuration "en" does not exist
The same error is shown when running the query in PgAdmin if search_path
doesn't contain 'dev' schema. With 'dev' in search_path, the query is ok.
I was expecting that 'currentSchema' connection parameter will be used to
resolve fts configuration to 'dev' schema.
