Re: Doc patch, index search_path where it's used to secure functions

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Doc patch, index search_path where it's used to secure functions
Date: 2012-11-14 02:46:19
Message-ID: 1352861179.26167.2.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2012-09-28 at 12:17 -0500, Karl O. Pinc wrote:
> On 09/28/2012 11:28:39 AM, Karl O. Pinc wrote:
>
> > Doc patch, index search_path where it's used to secure functions.
> > search_path-securing.patch
>
> Second version. Should be indexing the concept, not the run-time
> setting.

Well, I'm not sure. We currently have three index entries on the topic:

search path
search_path
search_path configuration parameter

I think I'd put them all under search_path.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2012-11-14 02:50:55 Re: Doc patch, further describe and-mask nature of the permission system
Previous Message Bruce Momjian 2012-11-14 00:51:45 Re: Further pg_upgrade analysis for many tables