| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Subject: | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| Date: | 2023-08-01 21:47:47 |
| Message-ID: | CAKFQuwbLmqsATUzFzqrrrVBC5ynVV3iETkpz8Hxvu57v3WgNuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, Aug 1, 2023 at 2:38 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Tue, 2023-08-01 at 11:16 -0700, David G. Johnston wrote:
> > They can use ALTER FUNCTION and the existing "FROM CURRENT"
> > specification to get back to current behavior if desired.
>
> The current behavior is that the search_path comes from the environment
> each execution. FROM CURRENT saves the search_path at definition time
> and uses that each execution.
>
>
Right...I apparently misread "create" as "the" in "when CREATE FUNCTION is
executed".
The overall point stands, it just requires defining a similar "FROM
SESSION" to allow for explicitly specifying the current default (missing)
behavior.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-08-01 22:00:16 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| Previous Message | Jeff Davis | 2023-08-01 21:38:30 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-08-01 22:00:16 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| Previous Message | Jeff Davis | 2023-08-01 21:38:30 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |