Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id EE463B61B35
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Tue, 31 May 2011 03:28:06 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 13249-06 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Tue, 31 May 2011 06:28:00 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-iy0-f174.google.com (mail-iy0-f174.google.com
	[209.85.210.174])
	by mail.postgresql.org (Postfix) with ESMTP id EEE35B61B2F
	for <pgsql-docs@postgresql.org>; Tue, 31 May 2011 03:27:59 -0300 (ADT)
Received: by iyb14 with SMTP id 14so3421576iyb.19
	for <pgsql-docs@postgresql.org>; Mon, 30 May 2011 23:27:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:date:message-id:subject:from:to
	:content-type; bh=eschbWTO2btRFICowl5MMAd7mHlS5q9/EYvulcBftQY=;
	b=iNEitmJ45s1mYlbIoFtYQ4Jrh1LPQJRVEFhoaC+vavqQQsG6GWkffuJTsuovnbmEHV
	1BvTvWqS4fY+bcp0sv5DCuJT90b1L3ytSSyZGXE0wKKgFOcepULaFz1ZvA7H+ivq+21q
	bpXBiTp6H0nMWn10s6tcK/uLgnjgSGRnK4BEs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=aJh0o5GtTOgA7V95+3ai6/AI+yoXlp+tBMPUeRCmL8phvwguZBPAliegh7RI3iEdXL
	jYFlb+r92r2rKkhvfJagHd1FRK3ed36+gilfdi2I0vMKrWb5+ZTGQ2SAdZuOWhaJ0zNE
	x8rgWaBMnwZVnrd6iHEjvfySdJrap6q7KuORM=
MIME-Version: 1.0
Received: by 10.231.60.73 with SMTP id o9mr7329234ibh.33.1306823279373; Mon,
	30 May 2011 23:27:59 -0700 (PDT)
Received: by 10.231.16.131 with HTTP; Mon, 30 May 2011 23:27:59 -0700 (PDT)
Date: Tue, 31 May 2011 16:27:59 +1000
Message-ID: <BANLkTikovATDon-Nhd1MPo4PytGJEfh5mQ@mail.gmail.com>
Subject: Add link to current_schemas in config.sgml
From: Brendan Jurd <direvus@gmail.com>
To: pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.888 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001,
	T_TO_NO_BRKTS_FREEMAIL=0.01
X-Spam-Level: 
X-Archive-Number: 201105/92
X-Sequence-Number: 6767

Hi folks,

This is just a quick docs patch to add a link to the mention of the
current_schemas function from 18.10.1. Statement Behavior.

The function must be called with one boolean argument, the meaning of
which isn't clear until you read the description in 9.23.

I also removed the parentheses after the function name as this was a)
misleading the reader into thinking the function could be called
without arguments and b) inconsistent with the style for referring to
functions elsewhere in the chapter.

Cheers,
BJ

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 3981969..c0ba5a5 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4485,10 +4485,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()</>.  This is not quite the same as
-        examining the value of <varname>search_path</varname>, since
-        <function>current_schemas()</> shows how the items
-        appearing in <varname>search_path</varname> were resolved.
+        <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 appearing in <varname>search_path</varname> were
+        resolved.
        </para>

        <para>