Re: Doc patch, normalize search_path in index

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Karl O. Pinc" <kop@meme.com>, pgsql-hackers@postgresql.org
Date: 2013-01-25T18:41:43Z
Lists: pgsql-hackers
On Fri, Jan 25, 2013 at 01:35:49PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I have applied a modified version of your patch that creates separate
> > secondary index references for search_path.
> 
> This patch seems pretty bizarre.  What is the difference between a
> "configuration parameter" and a "run-time setting"?  Why would you
> point people to two different places for those two terms?

I think he is trying to distinguish between the parameter and the
setting of the parameter, and also its use for security.  No one really
replied to the email so I thought the distinction was accpetable.

Should I make them both "configuration parameter" and leave the
"security" as a second one separate?

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. doc: Improve search_path mentions in index