Re: CREATE FUNCTION ... SEARCH { DEFAULT | SYSTEM | SESSION }
Maciek Sakrejda <m.sakrejda@gmail.com>
From: Maciek Sakrejda <m.sakrejda@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-09-20T06:25:13Z
Lists: pgsql-hackers
On Tue, Sep 19, 2023, 20:23 Maciek Sakrejda <m.sakrejda@gmail.com> wrote: > I wonder if something like CURRENT (i.e., the search path at function > creation time) might be a useful keyword addition. I can see some uses > (more forgiving than SYSTEM but not as loose as SESSION), but I don't > know if it would justify its presence. I realize now this is exactly what SET search_path FROM CURRENT does. Sorry for the noise. Regarding extensions installed in the public schema throwing a wrench in the works, is that still a problem if the public schema is not writable? I know that that's a new default, but it won't be forever.
Commits
-
Cache opaque handle for GUC option to avoid repeasted lookups.
- 867dd2dc8704 17.0 landed
-
Add cache for recomputeNamespacePath().
- f26c2368dcae 17.0 cited