Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit4ed6f6d

Browse files
author
Neil Conway
committed
Fix a typo in recent xfunc addition, do some routine SGML police work.
1 parent546d684 commit4ed6f6d

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

‎doc/src/sgml/xfunc.sgml

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.118 2006/11/2303:52:05 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.119 2006/11/2305:28:18 neilc Exp $ -->
22

33
<sect1 id="xfunc">
44
<title>User-Defined Functions</title>
@@ -1234,12 +1234,12 @@ PG_MODULE_MAGIC;
12341234
<para>
12351235
Optionally, a dynamically loaded file can contain initialization and
12361236
finalization functions. If the file includes a function named
1237-
<literal>_PG_init</>, that function will be called immediately after
1237+
<function>_PG_init</>, that function will be called immediately after
12381238
loading the file. The function receives no parameters and should
12391239
return void. If the file includes a function named
1240-
<literal>_PG_fini</>, that function will be called immediately before
1240+
<function>_PG_fini</>, that function will be called immediately before
12411241
unloading the file. Likewise, the function receives no parameters and
1242-
should return void. Note that <literal>_PG_fini</> will only be called
1242+
should return void. Note that <function>_PG_fini</> will only be called
12431243
during an unload of the file, not during process termination.
12441244
(Presently, an unload only happens in the context of re-loading
12451245
the file due to an explicit <command>LOAD</> command.)
@@ -2921,20 +2921,19 @@ CREATE FUNCTION make_array(anyelement) RETURNS anyarray
29212921
<programlisting>
29222922
void RequestAddinShmemSpace(int size)
29232923
</programlisting>
2924-
from your <literal>_PG_init</> function.
2924+
from your <function>_PG_init</> function.
29252925
</para>
29262926
<para>
29272927
LWLocks are reserved by calling:
29282928
<programlisting>
29292929
void RequestAddinLWLocks(int n)
29302930
</programlisting>
2931-
from <literal>_PG_init</>.
2931+
from <function>_PG_init</>.
29322932
</para>
29332933
<para>
29342934
To avoid possible race-conditions, each backend should use the LWLock
2935-
<literal>AddinShmemInitLock</> when connecting to andintializing
2935+
<function>AddinShmemInitLock</> when connecting to andinitializing
29362936
its allocation of shared memory, as shown here:
2937-
29382937
<programlisting>
29392938
static mystruct *ptr = NULL;
29402939

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp