| From: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE FUNCTION ... SEARCH { DEFAULT | SYSTEM | SESSION } |
| Date: | 2023-09-20 06:25:13 |
| Message-ID: | CAOtHd0BQHqZ5aR2vAojV0mVPTrzEGPBV0EXeANDeZMT6FxgwLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 19, 2023, 20:23 Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-09-20 06:42:26 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |
| Previous Message | Dilip Kumar | 2023-09-20 06:21:35 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |