database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-08 22:02:03 +03:00
Code

Fix some typos.

Browse Source
This commit is contained in:
Thomas G. Lockhart 1998-04-28 14:54:24 +00:00
parent 329949d1fe
commit db602e80ad
2 changed files with 22 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/src/sgml/dfunc.sgml
View File

@ -9,9 +9,9 @@
previously mentioned, <ProductName>Postgres</ProductName> loads your code at
runtime, as required. In order to allow your code to be
dynamically loaded, you may have to compile and
linkedit it in a special way. This section briefly
link-edit it in a special way. This section briefly
describes how to perform the compilation and
linkediting required before you can load your user-defined
link-editing required before you can load your user-defined
functions into a running <ProductName>Postgres</ProductName> server. Note that
this process has changed as of Version 4.2.
<Tip>
@ -140,7 +140,8 @@ The GNU C compiler usually does not provide the special
% cc -G 0 -c foo.c
</ProgramListing>
produces an object file called foo.o that can then be
dynamically loaded into <ProductName>Postgres</ProductName>. No additional loading or link-editing must be performed.
dynamically loaded into <ProductName>Postgres</ProductName>.
No additional loading or link-editing must be performed.
</Para>
</Sect1>
@ -149,7 +150,8 @@ The GNU C compiler usually does not provide the special
<Para>
Under DEC OSF/1, you can take any simple object file
and produce a shared object file by running the ld command over it with the correct options. The commands to
and produce a shared object file by running the ld command
over it with the correct options. The commands to
do this look like:
<ProgramListing>
# simple DEC OSF/1 example
@ -168,7 +170,8 @@ Actually, <ProductName>Postgres</ProductName> does not care
what you name the
file as long as it is a shared object file. If you prefer
to name your shared object files with the extension .o, this
is fine with <ProductName>Postgres</ProductName> so long as you make sure that the correct
is fine with <ProductName>Postgres</ProductName>
so long as you make sure that the correct
file name is given to the create function command. In
other words, you must simply be consistent. However, from a
pragmatic point of view, we discourage this practice because
@ -226,7 +229,11 @@ If the file you specify is
<ProgramListing>
# simple Solaris 2.x example
&percnt; cc -K PIC -c foo.c
&percnt; ld -G -Bdynamic -o foo.so foo.o
</ProgramListing>
or
<ProgramListing>
# simple Solaris 2.x example
&percnt; gcc -fPIC -c foo.c
&percnt; ld -G -Bdynamic -o foo.so foo.o
</ProgramListing>

2
doc/src/sgml/intro.sgml
View File

@ -275,7 +275,7 @@ Built-in types have been improved, including new wide-range date/time types and
</ListItem>
<ListItem>
<Para>
Overall backend code speed has been increased by approximately 20%, and backend startup speed has decreased 80%.
Overall backend code speed has been increased by approximately 20%, and backend startup time has decreased 80%.
</Para>
</ListItem>
</ItemizedList>