More minor SGML improvements for xfunc.sgml, including making some

titles more concise. (We usually don't need to repeat the name of a
section in the title of one of its subsections.)
This commit is contained in:
Neil Conway 2006-11-23 05:43:32 +00:00
parent ebf071643a
commit 34036c8658

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.119 2006/11/23 05:28:18 neilc Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.120 2006/11/23 05:43:32 neilc Exp $ -->
<sect1 id="xfunc">
<title>User-Defined Functions</title>
@ -1587,7 +1587,7 @@ memcpy(destination-&gt;data, buffer, 40);
</sect2>
<sect2>
<title>Calling Conventions Version 0 for C-Language Functions</title>
<title>Version 0 Calling Conventions</title>
<para>
We present the <quote>old style</quote> calling convention first &mdash; although
@ -1735,7 +1735,7 @@ CREATE FUNCTION concat_text(text, text) RETURNS text
</sect2>
<sect2>
<title>Calling Conventions Version 1 for C-Language Functions</title>
<title>Version 1 Calling Conventions</title>
<para>
The version-1 calling convention relies on macros to suppress most
@ -2261,7 +2261,7 @@ include $(PGXS)
<sect2>
<title>Composite-Type Arguments in C-Language Functions</title>
<title>Composite-Type Arguments</title>
<para>
Composite types do not have a fixed layout like C structures.
@ -2366,7 +2366,7 @@ CREATE FUNCTION c_overpaid(emp, integer) RETURNS boolean
</sect2>
<sect2>
<title>Returning Rows (Composite Types) from C-Language Functions</title>
<title>Returning Rows (Composite Types)</title>
<para>
To return a row or composite-type value from a C-language
@ -2517,7 +2517,7 @@ HeapTupleGetDatum(HeapTuple tuple)
</sect2>
<sect2 id="xfunc-c-return-set">
<title>Returning Sets from C-Language Functions</title>
<title>Returning Sets</title>
<para>
There is also a special API that provides support for returning
@ -2910,14 +2910,14 @@ CREATE FUNCTION make_array(anyelement) RETURNS anyarray
</para>
</sect2>
<sect2>
<title>Shared Memory and LWLocks in C-Language Functions</title>
<title>Shared Memory and LWLocks</title>
<para>
Add-ins may reserve LWLocks and an allocation of shared memory on server
startup. The add-in's shared library must be preloaded, by specifying
startup. The add-in's shared library must be preloaded by specifying
it in
<xref linkend="guc-shared-preload-libraries"><indexterm><primary>shared-preload-libraries</></>,
and the shared memory must be reserved by calling:
<xref linkend="guc-shared-preload-libraries"><indexterm><primary>shared-preload-libraries</></>.
Shared memory is reserved by calling:
<programlisting>
void RequestAddinShmemSpace(int size)
</programlisting>