Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
4ed6f6d4
Commit
4ed6f6d4
authored
Nov 23, 2006
by
Neil Conway
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix a typo in recent xfunc addition, do some routine SGML police work.
parent
546d6848
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
8 deletions
+7
-8
doc/src/sgml/xfunc.sgml
doc/src/sgml/xfunc.sgml
+7
-8
No files found.
doc/src/sgml/xfunc.sgml
View file @
4ed6f6d4
<!-- $PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.11
8 2006/11/23 03:52:05 momjian
Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.11
9 2006/11/23 05:28:18 neilc
Exp $ -->
<sect1 id="xfunc">
<title>User-Defined Functions</title>
...
...
@@ -1234,12 +1234,12 @@ PG_MODULE_MAGIC;
<para>
Optionally, a dynamically loaded file can contain initialization and
finalization functions. If the file includes a function named
<
literal
>_PG_init</>, that function will be called immediately after
<
function
>_PG_init</>, that function will be called immediately after
loading the file. The function receives no parameters and should
return void. If the file includes a function named
<
literal
>_PG_fini</>, that function will be called immediately before
<
function
>_PG_fini</>, that function will be called immediately before
unloading the file. Likewise, the function receives no parameters and
should return void. Note that <
literal
>_PG_fini</> will only be called
should return void. Note that <
function
>_PG_fini</> will only be called
during an unload of the file, not during process termination.
(Presently, an unload only happens in the context of re-loading
the file due to an explicit <command>LOAD</> command.)
...
...
@@ -2921,20 +2921,19 @@ CREATE FUNCTION make_array(anyelement) RETURNS anyarray
<programlisting>
void RequestAddinShmemSpace(int size)
</programlisting>
from your <
literal
>_PG_init</> function.
from your <
function
>_PG_init</> function.
</para>
<para>
LWLocks are reserved by calling:
<programlisting>
void RequestAddinLWLocks(int n)
</programlisting>
from <
literal
>_PG_init</>.
from <
function
>_PG_init</>.
</para>
<para>
To avoid possible race-conditions, each backend should use the LWLock
<
literal>AddinShmemInitLock</> when connecting to and in
tializing
<
function>AddinShmemInitLock</> when connecting to and ini
tializing
its allocation of shared memory, as shown here:
<programlisting>
static mystruct *ptr = NULL;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment