| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <jdavis(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| Date: | 2023-06-13 15:24:27 |
| Message-ID: | CA+Tgmobx+9YpKpG03ZwvP0+ZYG=KJTsteCsNkgkQq1ZOzOrO8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Jun 12, 2023 at 8:20 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> I followed the rules here for "Writing SECURITY DEFINER Functions
> Safely":
>
> https://www.postgresql.org/docs/16/sql-createfunction.html
>
> which suggests adding pg_temp at the end (otherwise it is searched
> first by default).
Interesting. The issue of "what is a safe search path?" is more
nuanced than I would prefer. :-(
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2023-06-13 18:29:20 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| Previous Message | Peter Eisentraut | 2023-06-13 13:12:16 | pgsql: doc: Move list entry to proper position |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | torikoshia | 2023-06-13 15:49:39 | Re: Allow pg_archivecleanup to remove backup history files |
| Previous Message | torikoshia | 2023-06-13 15:22:14 | Re: RFC: Logging plan of the running query |