| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Gurjeet Singh <gurjeet(at)singh(dot)im>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Fix search_path for all maintenance commands |
| Date: | 2023-07-17 19:16:25 |
| Message-ID: | 2ad1dd4e5be5567c0d75676b348eab33b529e974.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2023-07-17 at 10:58 -0700, Nathan Bossart wrote:
> On Sat, Jul 15, 2023 at 02:13:33PM -0700, Noah Misch wrote:
> > The 2018 security fixes instigated many function repairs that
> > $SUBJECT would
> > otherwise instigate. That wasn't too painful. The net new pain of
> > $SUBJECT
> > will be less, since the 2018 security fixes prepared the path.
> > Hence, I
> > remain +1 for the latest Davis proposal.
>
> I concur.
Based on feedback, I plan to commit soon.
Tom's objection seemed specific to v16, and Robert's concern seemed to
be about having the MAINTAIN privilege without this patch. If I missed
any objections to this patch, please let me know.
If we hear about breakage that suggests we need an escape hatch GUC, we
have time to add one later.
I remain open to considering more complete fixes for the search_path
problems.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-07-17 19:43:10 | Re: MERGE ... RETURNING |
| Previous Message | Nathan Bossart | 2023-07-17 18:47:12 | Re: Should we remove db_user_namespace? |