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
fde65267
Commit
fde65267
authored
Aug 17, 1998
by
Thomas G. Lockhart
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Make small sentence cleanups. Add missing formatting for program example.
parent
28742a18
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
14 deletions
+17
-14
doc/src/sgml/start-ag.sgml
doc/src/sgml/start-ag.sgml
+17
-14
No files found.
doc/src/sgml/start-ag.sgml
View file @
fde65267
...
...
@@ -17,12 +17,12 @@
shows how the <ProductName>Postgres</ProductName> distribution is laid
out when installed in the default way. For simplicity,
we will assume that <ProductName>Postgres</ProductName> has been installed in the
directory <
FileName>/usr/local/pgsql</FileN
ame>. Therefore, wherever
you see the directory <
FileName>/usr/local/pgsql</FileN
ame> you should
directory <
filename>/usr/local/pgsql</filen
ame>. Therefore, wherever
you see the directory <
filename>/usr/local/pgsql</filen
ame> you should
substitute the name of the directory where <ProductName>Postgres</ProductName> is
actually installed.
All <ProductName>Postgres</ProductName> commands are installed in the directory
<
FileName>/usr/local/pgsql/bin</FileN
ame>. Therefore, you should add
<
filename>/usr/local/pgsql/bin</filen
ame>. Therefore, you should add
this directory to your shell command path. If you use
a variant of the Berkeley C shell, such as csh or tcsh,
you would add
...
...
@@ -115,6 +115,7 @@ incorporated into postgresql distribution.
and this caused a lot of problems). Latest perl has also support of locale and if locale is broken perl -v will
complain something like:
<programlisting>
8:17[mira]:~/WWW/postgres>setenv LC_CTYPE not_exist
8:18[mira]:~/WWW/postgres>perl -v
perl: warning: Setting locale failed.
...
...
@@ -124,6 +125,7 @@ incorporated into postgresql distribution.
LANG = (unset)
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
</programlisting>
</Para>
</ListItem>
...
...
@@ -131,9 +133,10 @@ incorporated into postgresql distribution.
<Para>
Wrong location of locale files!
Possible location: <FileName>/usr/lib/locale</FileName> (Linux, Solaris), <FileName>/usr/share/locale</FileName> (Linux), <FileName>/usr/lib/nls/loc</FileName> (DUX 4.0)
Check man locale for right place. Under Linux I did a symbolical link between <FileName>/usr/lib/locale</FileName> and
<FileName>/usr/share/locale</FileName> to be sure next libc will not break my locale.
Possible locations include: <filename>/usr/lib/locale</filename> (Linux, Solaris), <filename>/usr/share/locale</filename> (Linux), <filename>/usr/lib/nls/loc</filename> (DUX 4.0)
Check <command>man locale</command> to find the correct location.
Under Linux I did a symbolic link between <filename>/usr/lib/locale</filename> and
<filename>/usr/share/locale</filename> to be sure that the next libc will not break my locale.
</Para>
</ListItem>
</ItemizedList>
...
...
@@ -143,13 +146,13 @@ incorporated into postgresql distribution.
<Para>
You can use ~* and order by operators for strings contain characters from national alphabets. Non-english users
definitely need that. If you won't use locale stuff just undefine USE_LOCALE variable.
definitely need that. If you won't use locale stuff just undefine
the
USE_LOCALE variable.
<Sect2>
<Title>What are the Drawbacks?</Title>
<Para>
There is one evident drawback of using locale - it's speed
! So, use locale only if you really need it.
There is one evident drawback of using locale - it's speed! So, use locale only if you really need it.
</Chapter>
...
...
@@ -233,21 +236,21 @@ managing disk storage.
Remember that database creation is actually performed by the database backend.
Therefore, any environment variable specifying an alternate location must have
been defined before the backend was started. To define an alternate location
PGDATA2 pointing to <
FileName>/home/postgres/data</FileN
ame>, type
PGDATA2 pointing to <
filename>/home/postgres/data</filen
ame>, type
<ProgramListing>
% setenv PGDATA2 /home/postgres/data
</ProgramListing>
<Para>
Usually, you will want to define this variable in the <ProductName>Postgres</ProductName> superuser's
<
FileName>.profile</FileN
ame>
<
filename>.profile</filen
ame>
or
<
FileName>.cshrc</FileN
ame>
<
filename>.cshrc</filen
ame>
initialization file to ensure that it is defined upon system startup.
<Para>
To create a data storage area in <
FileName>/home/postgres/data</FileN
ame>, ensure
that <
FileName>/home/postgres</FileN
ame> already exists and is writable.
To create a data storage area in <
filename>/home/postgres/data</filen
ame>, ensure
that <
filename>/home/postgres</filen
ame> already exists and is writable.
From the command line, type
<ProgramListing>
% initlocation $PGDATA2
...
...
@@ -274,7 +277,7 @@ To test the new location, create a database <Database>test</Database> by typing
started the <Application>postmaster</Application> process and authorized you to
use the database, you (as a user) may begin to start up
applications. As previously mentioned, you should add
<
FileName>/usr/local/pgsql/bin</FileN
ame> to your shell search path.
<
filename>/usr/local/pgsql/bin</filen
ame> to your shell search path.
In most cases, this is all you should have to do in
terms of preparation.
...
...
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