Re: pgsql: Fix search_path to a safe value during maintenance operations.

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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 21:38:30
Message-ID: 3c6f92439fef0137b56d68eae54256296bda9320.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 11:16 -0700, David G. Johnston wrote:
> They can use ALTER FUNCTION and the existing "FROM CURRENT"
> specification to get back to current behavior if desired.

The current behavior is that the search_path comes from the environment
each execution. FROM CURRENT saves the search_path at definition time
and uses that each execution.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message David G. Johnston 2023-08-01 21:47:47 Re: pgsql: Fix search_path to a safe value during maintenance operations.
Previous Message Andres Freund 2023-08-01 21:18:03 pgsql: Fix pg_stat_io buffer reuse test instability

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2023-08-01 21:47:47 Re: pgsql: Fix search_path to a safe value during maintenance operations.
Previous Message Andres Freund 2023-08-01 21:19:45 Re: stats test intermittent failure