On Thu, Jul 8, 2021 at 1:09 PM Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
This isn't the only SQL syntax that has implicit operators; CASE is
another example, and I think there are more. We've discussed inventing
non-SQL-spec syntax that can cope with explicitly writing a qualified
operator name in all these cases, but it looks like a messy project
with an ugly final result :-(, so nothing's been done yet.
(sorry if this is a duplicate, got an error on my first sending attempt)
IIUC, functions can force a search_path even during dump/restore by being created with one specified as part of the create function command. Since the issue is with stored objects moreso than queries generically is it feasible to approach the view solution by adding a "SET" clause to CREATE VIEW as well?
