Horton

Re: CREATE FUNCTION ... SEARCH { DEFAULT | SYSTEM | SESSION }

Peter Eisentraut <peter@eisentraut.org>

View thread View on postgr.es
From: Peter Eisentraut <peter@eisentraut.org>
To: Jeff Davis <pgsql@j-davis.com>, pgsql-hackers@postgresql.org
Date: 2023-08-16T06:51:25Z
Lists: pgsql-hackers 
On 12.08.23 04:35, Jeff Davis wrote:
> The attached patch implements a new SEARCH clause for CREATE FUNCTION.
> The SEARCH clause controls the search_path used when executing
> functions that were created without a SET clause.

I don't understand this.  This adds a new option for cases where the 
existing option wasn't specified.  Why not specify the existing option 
then?  Is it not good enough?  Can we improve it?

Commits

  1. Cache opaque handle for GUC option to avoid repeasted lookups.

  2. Add cache for recomputeNamespacePath().