| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(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 23:40:45 |
| Message-ID: | de985b794d89f8661b920b18ed7b10ae21523333.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, 2023-08-01 at 14:47 -0700, David G. Johnston wrote:
> The overall point stands, it just requires defining a similar "FROM
> SESSION" to allow for explicitly specifying the current default
> (missing) behavior.
That sounds useful as a way to future-proof function definitions that
intend to use the session search_path.
It seems like we're moving in the direction of search_path defaulting
to FROM CURRENT (probably with a long road of compatibility GUCs to
minimize breakage...) and everything else defaulting to FROM SESSION
(as before)?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2023-08-02 00:05:58 | pgsql: Fix performance regression in pg_strtointNN_safe functions |
| Previous Message | Jeff Davis | 2023-08-01 22:00:16 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Imseih (AWS), Sami | 2023-08-01 23:59:12 | Re: Correct the documentation for work_mem |
| Previous Message | Jeff Davis | 2023-08-01 23:39:54 | Re: Incorrect handling of OOM in WAL replay leading to data loss |