Re: Fix search_path for all maintenance commands - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Fix search_path for all maintenance commands
Date
Msg-id bd46ea3bd255d4683dddef44ed28743af87862d9.camel@j-davis.com
Whole thread Raw
In response to Re: Fix search_path for all maintenance commands  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Fix search_path for all maintenance commands
List pgsql-hackers
On Thu, 2023-06-08 at 21:55 -0700, Nathan Bossart wrote:
> On Thu, Jun 08, 2023 at 06:08:08PM -0400, Greg Stark wrote:
> > I guess that's pretty narrow and a reasonable thing to desupport.
> > Users could just mark those functions with search_path or schema
> > qualify the object references in them. Perhaps we should also be
> > picking up cases like that sooner so users realize they've created
> > a
> > footgun for themselves?

Many cases will be picked up, for instance CREATE INDEX will error if
the safe search path is not good enough.

> I'm inclined to agree that this is reasonable to desupport.

Committed.

> I bet we could skip forcing the search_path for maintenance commands
> run as
> the table owner, but such a discrepancy seems likely to cause far
> more
> confusion than anything else.

Agreed.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: win32ver data in meson-built postgres.exe
Next
From: Gregory Smith
Date:
Subject: Re: index prefetching