Re: Doc patch, normalize search_path in index
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: "Karl O. Pinc" <kop@meme.com>
Cc: pgsql-hackers@postgresql.org
Date: 2013-01-25T17:50:03Z
Lists: pgsql-hackers
Attachments
- search_path.diff (text/x-diff) patch
On Fri, Sep 28, 2012 at 12:40:38PM -0500, Karl O. Pinc wrote: > Hi, > > The attached patch (against git head) > normalizes "search_path" as the thing indexed > and uses a secondary index term to distinguish > the configuration parameter from the run-time > setting. > > "search path" the concept remains distinguished > in the index from "search_path" the setting/config param. > It's hard to say whether it's useful to make this > distinction. From a practical perspective it's easy > for the eye to stop scanning when the indent > level changes and so fail to notice that both > "search path" and "search_path" are index > entries. At least the index is a > lot more tidy than before. I have applied a modified version of your patch that creates separate secondary index references for search_path. -- 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 →
-
doc: Improve search_path mentions in index
- a301eb99c953 9.3.0 cited