1
0
mirror of https://github.com/postgres/postgres.git synced 2025-12-19 17:02:53 +03:00

Use PostgreSQL consistantly throughout docs. Before, usage was split evenly

between Postgres and PostgreSQL.
This commit is contained in:
Thomas G. Lockhart
2001-12-08 03:24:40 +00:00
parent 68cb184b56
commit 03a321d214
91 changed files with 360 additions and 340 deletions

View File

@@ -1,6 +1,6 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.25 2001/12/04 21:19:57 tgl Exp $
Postgres documentation
$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.26 2001/12/08 03:24:34 thomas Exp $
PostgreSQL documentation
-->
<refentry id="SQL-COPY">
@@ -172,7 +172,7 @@ ERROR: <replaceable>reason</replaceable>
</title>
<para>
<command>COPY</command> moves data between
<productname>Postgres</productname> tables and
<productname>PostgreSQL</productname> tables and
standard file-system files.
<command>COPY TO</command> copies the entire contents of a table to
@@ -182,7 +182,7 @@ ERROR: <replaceable>reason</replaceable>
<para>
<command>COPY</command> with a filename instructs
the <productname>Postgres</productname> backend
the <productname>PostgreSQL</productname> backend
to directly read from or write to a file.
The file must be accessible to the backend and the name must be specified
from the viewpoint of the backend.
@@ -262,7 +262,8 @@ ERROR: <replaceable>reason</replaceable>
directly by the backend, not by the client application. Therefore,
they must reside on or be accessible to the database server machine,
not the client. They must be accessible to and readable or writable
by the Postgres user (the userid the backend runs as), not the client.
by the <application>PostgreSQL</application> user (the userid the
backend runs as), not the client.
<command>COPY</command> naming a file is only allowed to database
superusers, since it allows writing on any file that the backend has
privileges to write on.
@@ -343,7 +344,7 @@ ERROR: <replaceable>reason</replaceable>
as the column delimiter, backslash that delimiter character to include
it in data.) A literal newline character is
represented as a backslash and a newline. When loading text data
not generated by <acronym>Postgres</acronym>,
not generated by <application>PostgreSQL</application>,
you will need to convert backslash
characters ("\") to double-backslashes ("\\") to ensure that they
are loaded properly.
@@ -357,7 +358,8 @@ ERROR: <replaceable>reason</replaceable>
<title>Binary Format</title>
<para>
The file format used for <command>COPY BINARY</command> changed in
Postgres v7.1. The new format consists of a file header, zero or more
<application>PostgreSQL</application> v7.1.
The new format consists of a file header, zero or more
tuples, and a file trailer.
</para>