config.sgml referring to unix_socket_directories on older releases

Started by Guillaume Lelargeover 11 years ago2 messages
#1Guillaume Lelarge
guillaume@lelarge.info
1 attachment(s)

Hi,

While updating the french translation of the latest releases, I stumbled
upon a small issue on the config.sgml file.

It talks about unix_socket_directories whereas this parameter only appears
with the 9.3 release. It should probably be replaced with
unix_socket_directory for all releases where this has been commited (8.4 to
9.2). The patch attached does this. It applies cleanly on all releases
(with a hunk though).

Thanks.

Regards.

--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com

Attachments:

unix_socket_directory.patchtext/x-patch; charset=US-ASCII; name=unix_socket_directory.patchDownload
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index d47dd9c..9f23e8c 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -473,7 +473,7 @@ SET ENABLE_SEQSCAN TO OFF;
        <para>
         This parameter is irrelevant on systems, notably Solaris as of Solaris
         10, that ignore socket permissions entirely.  There, one can achieve a
-        similar effect by pointing <varname>unix_socket_directories</> to a
+        similar effect by pointing <varname>unix_socket_directory</> to a
         directory having search permission limited to the desired audience.
         This parameter is also irrelevant on Windows, which does not have
         Unix-domain sockets.
#2Fujii Masao
masao.fujii@gmail.com
In reply to: Guillaume Lelarge (#1)
Re: config.sgml referring to unix_socket_directories on older releases

On Sun, Jul 27, 2014 at 12:09 AM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:

Hi,

While updating the french translation of the latest releases, I stumbled
upon a small issue on the config.sgml file.

It talks about unix_socket_directories whereas this parameter only appears
with the 9.3 release. It should probably be replaced with
unix_socket_directory for all releases where this has been commited (8.4 to
9.2). The patch attached does this. It applies cleanly on all releases (with
a hunk though).

Thanks for the patch! Applied it to 9.2, 9.1 and 9.0. I didn't applied it to 8.4
because it's already EOL.

Regards,

--
Fujii Masao

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers