aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2011-06-13 13:02:54 -0400
committerRobert Haas <rhaas@postgresql.org>2011-06-13 13:04:07 -0400
commit20c73f3a327d2289871e7701e8325e5e3ebe518c (patch)
tree8e64b9c63407ea7d238afba41178a8c7c35a7bbd
parent26e7eec5f07c5dfb4b57f374bf01185edd88cf73 (diff)
downloadpostgresql-20c73f3a327d2289871e7701e8325e5e3ebe518c.tar.gz
postgresql-20c73f3a327d2289871e7701e8325e5e3ebe518c.zip
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.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 3d9c3a0ca98..e835e4bc909 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4491,11 +4491,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>