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 1cb41fed6554739b0adc04602a7f63af0ceee4f0.camel@j-davis.com
Whole thread Raw
In response to Re: Fix search_path for all maintenance commands  (Isaac Morland <isaac.morland@gmail.com>)
List pgsql-hackers
On Tue, 2023-10-31 at 13:16 -0400, Isaac Morland wrote:
> Perhaps the search_path for running a maintenance command should be
> the search_path set for the table owner (ALTER ROLE … SET search_path
> …)?

After some thought, I don't think that's the right approach. It adds
another way search path can be changed, which adds to the complexity.

Also, by default it's "$user", public; and given that "public" was
world-writable until recently, that doesn't seem like a good idea for a
change intended to prevent search_path manipulation.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Compiler warning on Debian 12, PostgreSQL 16 Beta3
Next
From: "Tristan Partin"
Date:
Subject: Fix use of openssl.path() if openssl isn't found