mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-15 08:20:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix suggestions on file protection for alternate DB locations.

Browse Source
This commit is contained in:
Thomas G. Lockhart 1998-07-08 13:54:26 +00:00
parent ba3a99f193
commit 03fb60c52e
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/ref/create_database.sgml
View File

@ -157,7 +157,7 @@ There was a problem with creating the required directory; this operation will
To create a new database:
</PARA>
<ProgramListing>
<prompt>olly=></prompt></computeroutput> <userinput>create database lusiadas;</userinput>
<prompt>olly=></prompt> <userinput>create database lusiadas;</userinput>
</ProgramListing>
<PARA>
To create a new database in an alternate area <filename>~/private_db</filename>:
@ -189,7 +189,9 @@ There was a problem with creating the required directory; this operation will
There are security and data integrity issues involved with using alternate database locations
specified with absolute path names. See the Administrator's Guide for more information.
</PARA>
<!-- ------------------
</refsect1>
<!--
comment from Olly; response from Thomas...
<comment>
initlocation does not create a PG_VERSION file in the specified location.
@ -198,8 +200,7 @@ comment from Olly; response from Thomas...
</comment>
Hmm. This isn't an issue since the upgrade would do a dump/reload from the main database area also.
Not sure if the dump/reload would guarantee that the alternate data area gets refreshed though...
-------------------- -->
</refsect1>
-->
<REFSECT1 ID="R1-SQL-CREATEDATABASE-4">
<TITLE>