From: Tom Lane <tgl@sss.pgh.pa.us>
To: equincerot@yahoo.fr
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17483: postgres_fdw used with text to_tsvector and custom
 search configuration
In-reply-to: <1322024.1652712576@sss.pgh.pa.us>
References: <17483-795757fa99607659@postgresql.org>
 <1322024.1652712576@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 16 May 2022 10:49:36 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <466318.1658098780.1@sss.pgh.pa.us>
Date: Sun, 17 Jul 2022 18:59:40 -0400
Message-ID: <466319.1658098780@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/466319.1658098780%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> PG Bug reporting form <noreply@postgresql.org> writes:
>> I have an issue with the evaluation of to_tsvector and custom search
>> configuration through foreign data wrapper (from PG to PG).

> The other thing you're running into is that if the text search
> config isn't defined in the pg_catalog schema, it's not visible
> in the restricted search path that the remote session will use.
> The query shipped to the far end should handle that by writing
> "'public.custom_search'::regconfig", but it evidently doesn't ---
> that feels like a bug, indeed.

FYI, I've now pushed a fix for that problem; it'll be in the
August minor releases.

Also, beginning in v16, it'll be necessary to ensure that any
custom TS configuration you want to use this way belongs to
an extension that the foreign server considers "shippable"
(see postgres_fdw documentation).  We won't enforce that in
existing branches, though.

			regards, tom lane