diff options
| author | Robert Haas <rhaas@postgresql.org> | 2011-06-13 13:02:54 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2011-06-13 13:04:13 -0400 |
| commit | 6350d75bf2faa81cf7b8ccd3ceeb5fe4adefc7f5 (patch) | |
| tree | 034277d096e08c0bf4e0da98335fe6ba5f726cbe | |
| parent | c06bdaf92c78d3d5bc6efdc4474abbf33ab7a047 (diff) | |
Remove parentheses from mention of current_schemas function.
This is more consistent with what we do elsewhere, and hopefully avoids
creating the perception that current_schemas takes no arguments.
As suggested by Brendan Jurd
| -rw-r--r-- | doc/src/sgml/config.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 16d7433c2a3..32bccb41c9f 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -4285,11 +4285,11 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; <para> The current effective value of the search path can be examined via the <acronym>SQL</acronym> function - <function>current_schemas()</> + <function>current_schemas</> (see <xref linkend="functions-info">). This is not quite the same as examining the value of <varname>search_path</varname>, since - <function>current_schemas()</> shows how the items + <function>current_schemas</> shows how the items appearing in <varname>search_path</varname> were resolved. </para> |