mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Fix spacing in verbatim environments

Browse Source
This commit is contained in:
Peter Eisentraut 2014-07-08 11:39:07 -04:00
parent 6048896e4c
commit 53166fe248
7 changed files with 96 additions and 95 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/config.sgml
View File

@ -279,15 +279,15 @@ include 'filename'
Another possibility is to create a configuration file directory and Another possibility is to create a configuration file directory and
put this information into files there. For example, a <filename>conf.d</> put this information into files there. For example, a <filename>conf.d</>
directory could be referenced at the end of<filename>postgresql.conf</>: directory could be referenced at the end of<filename>postgresql.conf</>:
<screen> <programlisting>
include_dir 'conf.d' include_dir 'conf.d'
</screen> </programlisting>
Then you could name the files in the <filename>conf.d</> directory like this: Then you could name the files in the <filename>conf.d</> directory like this:
<screen> <programlisting>
00shared.conf 00shared.conf
01memory.conf 01memory.conf
02server.conf 02server.conf
</screen> </programlisting>
This shows a clear order in which these files will be loaded. This is This shows a clear order in which these files will be loaded. This is
important because only the last setting encountered when the server is important because only the last setting encountered when the server is
reading its configuration will be used. Something set in reading its configuration will be used. Something set in
@ -298,11 +298,11 @@ include 'filename'
<para> <para>
You might instead use this configuration directory approach while naming You might instead use this configuration directory approach while naming
these files more descriptively: these files more descriptively:
<screen> <programlisting>
00shared.conf 00shared.conf
01memory-8GB.conf 01memory-8GB.conf
02server-foo.conf 02server-foo.conf
</screen> </programlisting>
This sort of arrangement gives a unique name for each configuration file This sort of arrangement gives a unique name for each configuration file
variation. This can help eliminate ambiguity when several servers have variation. This can help eliminate ambiguity when several servers have
their configurations all stored in one place, such as in a version their configurations all stored in one place, such as in a version

20
doc/src/sgml/extend.sgml
View File

@ -1167,12 +1167,12 @@ include $(PGXS)
This procedure is also called a This procedure is also called a
<indexterm><primary>VPATH</primary></indexterm><firstterm>VPATH</firstterm> <indexterm><primary>VPATH</primary></indexterm><firstterm>VPATH</firstterm>
build. Here's how: build. Here's how:
<screen> <programlisting>
<userinput>mkdir build_dir</userinput> mkdir build_dir
<userinput>cd build_dir</userinput> cd build_dir
<userinput>make -f /path/to/extension/source/tree/Makefile</userinput> make -f /path/to/extension/source/tree/Makefile
<userinput>make -f /path/to/extension/source/tree/Makefile install</userinput> make -f /path/to/extension/source/tree/Makefile install
</screen> </programlisting>
</para> </para>
<para> <para>
@ -1181,10 +1181,10 @@ include $(PGXS)
core script <filename>config/prep_buildtree</>. Once this has been done core script <filename>config/prep_buildtree</>. Once this has been done
you can build by setting the <literal>make</literal> variable you can build by setting the <literal>make</literal> variable
<varname>USE_VPATH</varname> like this: <varname>USE_VPATH</varname> like this:
<screen> <programlisting>
<userinput>make USE_VPATH=/path/to/extension/source/tree</userinput> make USE_VPATH=/path/to/extension/source/tree
<userinput>make USE_VPATH=/path/to/extension/source/tree install</userinput> make USE_VPATH=/path/to/extension/source/tree install
</screen> </programlisting>
This procedure can work with a greater variety of directory layouts. This procedure can work with a greater variety of directory layouts.
</para> </para>

1
doc/src/sgml/logicaldecoding.sgml
View File

@ -326,6 +326,7 @@ typedef struct OutputPluginCallbacks
LogicalDecodeCommitCB commit_cb; LogicalDecodeCommitCB commit_cb;
LogicalDecodeShutdownCB shutdown_cb; LogicalDecodeShutdownCB shutdown_cb;
} OutputPluginCallbacks; } OutputPluginCallbacks;
typedef void (*LogicalOutputPluginInit)(struct OutputPluginCallbacks *cb); typedef void (*LogicalOutputPluginInit)(struct OutputPluginCallbacks *cb);
</programlisting> </programlisting>
The <function>begin_cb</function>, <function>change_cb</function> The <function>begin_cb</function>, <function>change_cb</function>