mirror of
https://github.com/postgres/postgres.git
synced 2025-12-21 05:21:08 +03:00
Spell checker run
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.33 2004/05/06 16:59:16 momjian Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.34 2004/12/13 18:05:10 petere Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@@ -57,7 +57,7 @@ ALTER USER <replaceable class="PARAMETER">name</replaceable> RESET <replaceable>
|
||||
The second variant changes the name of the user. Only a database
|
||||
superuser can rename user accounts. The session user cannot be
|
||||
renamed. (Connect as a different user if you need to do that.)
|
||||
Because <literal>MD5</>-encrypted passwords use the username as
|
||||
Because <literal>MD5</>-encrypted passwords use the user name as
|
||||
cryptographic salt, renaming a user clears their <literal>MD5</>
|
||||
password.
|
||||
</para>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.61 2004/12/02 15:32:53 momjian Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.62 2004/12/13 18:05:10 petere Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@@ -231,7 +231,7 @@ COPY <replaceable class="parameter">tablename</replaceable> [ ( <replaceable cla
|
||||
<listitem>
|
||||
<para>
|
||||
In <literal>CSV</> <command>COPY FROM</> mode, process each
|
||||
specified column as though it were quoted and hance not a
|
||||
specified column as though it were quoted and hence not a
|
||||
<literal>NULL</> value. For the default <literal>null string</> in
|
||||
<literal>CSV</> mode (<literal>''</>), this causes a missing
|
||||
values to be input as a zero-length strings.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/create_cast.sgml,v 1.19 2004/11/27 21:27:07 petere Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/create_cast.sgml,v 1.20 2004/12/13 18:05:10 petere Exp $ -->
|
||||
|
||||
<refentry id="SQL-CREATECAST">
|
||||
<refmeta>
|
||||
@@ -198,7 +198,7 @@ SELECT 'The time is ' || CAST(now() AS text);
|
||||
(Bizarrely, the SQL spec demands different behaviors for explicit and
|
||||
implicit casts in some cases. This argument is supplied for functions
|
||||
that must implement such casts. It is not recommended that you design
|
||||
your own datatypes so that this matters.)
|
||||
your own data types so that this matters.)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -219,7 +219,7 @@ SELECT 'The time is ' || CAST(now() AS text);
|
||||
represents converting from one type to another and applying a length
|
||||
coercion in a single step. When no such entry is available, coercion
|
||||
to a type that uses a type modifier involves two steps, one to
|
||||
convert between datatypes and a second to apply the modifier.
|
||||
convert between data types and a second to apply the modifier.
|
||||
</para>
|
||||
|
||||
</refsect1>
|
||||
@@ -251,7 +251,7 @@ SELECT 'The time is ' || CAST(now() AS text);
|
||||
<para>
|
||||
While not required, it is recommended that you continue to follow this old
|
||||
convention of naming cast implementation functions after the target data
|
||||
type. Many users are used to being able to cast datatypes using a
|
||||
type. Many users are used to being able to cast data types using a
|
||||
function-style notation, that is
|
||||
<replaceable>typename</>(<replaceable>x</>). This notation is in fact
|
||||
nothing more nor less than a call of the cast implementation function; it
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.87 2004/11/27 21:27:07 petere Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.88 2004/12/13 18:05:10 petere Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@@ -974,11 +974,12 @@ CREATE TABLE cinemas (
|
||||
</refsect2>
|
||||
|
||||
<refsect2>
|
||||
<title>TABLESPACE and USING INDEX TABLESPACE</title>
|
||||
<title>Tablespaces</title>
|
||||
|
||||
<para>
|
||||
The <productname>PostgreSQL</productname> concept of tablespaces is not
|
||||
standard.
|
||||
part of the standard. Hence, the clauses <literal>TABLESPACE</literal>
|
||||
and <literal>USING INDEX TABLESPACE</literal> are extensions.
|
||||
</para>
|
||||
</refsect2>
|
||||
</refsect1>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.25 2004/11/27 21:27:07 petere Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.26 2004/12/13 18:05:10 petere Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@@ -136,7 +136,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE <replaceable>table_name
|
||||
linkend="sql-selectinto" endterm="sql-selectinto-title">, but it is
|
||||
preferred since it is less likely to be confused with other uses of
|
||||
the <command>SELECT INTO</> syntax. Furthermore, <command>CREATE
|
||||
TABLE AS</command> offers a superset of the functionality offerred
|
||||
TABLE AS</command> offers a superset of the functionality offered
|
||||
by <command>SELECT INTO</command>.
|
||||
</para>
|
||||
|
||||
@@ -150,13 +150,13 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE <replaceable>table_name
|
||||
frequently executed, the OID counter would be rapidly
|
||||
incremented. As of <productname>PostgresSQL</productname> 8.0,
|
||||
the <command>CREATE TABLE AS</command> command allows the user to
|
||||
explicitely specify whether OIDs should be included. If the
|
||||
presence of OIDs is not explicitely specified,
|
||||
explicitly specify whether OIDs should be included. If the
|
||||
presence of OIDs is not explicitly specified,
|
||||
the <xref linkend="guc-default-with-oids"> configuration variable is
|
||||
used. While this variable currently defaults to true, the default
|
||||
value may be changed in the future. Therefore, applications that
|
||||
require OIDs in the table created by <command>CREATE TABLE
|
||||
AS</command> should explicitely specify <literal>WITH
|
||||
AS</command> should explicitly specify <literal>WITH
|
||||
OIDS</literal> to ensure compatibility with future versions
|
||||
of <productname>PostgreSQL</productname>.
|
||||
</para>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.123 2004/10/06 18:39:15 momjian Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.124 2004/12/13 18:05:10 petere Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@@ -493,7 +493,7 @@ PostgreSQL documentation
|
||||
these options are required, defaults do apply. If you omit the host
|
||||
name, <application>psql</> will connect via a Unix domain socket
|
||||
to a server on the local host, or via TCP/IP to <literal>localhost</> on machines
|
||||
that don't have unix domain sockets. The default port number is compile-time determined.
|
||||
that don't have Unix domain sockets. The default port number is compile-time determined.
|
||||
Since the database server uses the same default, you will not have
|
||||
to specify the port in most cases. The default user name is your
|
||||
Unix user name, as is the default database name. Note that you can't
|
||||
@@ -1603,7 +1603,7 @@ lo_import 152801
|
||||
class="parameter">filename</replaceable> is omitted, the history
|
||||
is written to the standard output. This option is only available
|
||||
if <application>psql</application> is configured to use the
|
||||
<acronym>GNU</acronym> readline (or history) library.
|
||||
<acronym>GNU</acronym> <application>Readline</application> library.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
@@ -2368,7 +2368,7 @@ testdb=> <userinput>\set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\'
|
||||
Prompts may contain terminal control characters which, for
|
||||
example, change the color, background, or style of the prompt
|
||||
text, or change the title of the terminal window. In order for
|
||||
the line editing features of readline to work properly, these
|
||||
the line editing features of <application>Readline</application> to work properly, these
|
||||
non-printing control characters must be designated as invisible
|
||||
by surrounding them with <literal>%[</literal> and
|
||||
<literal>%]</literal>. Multiple pairs of these may occur within
|
||||
|
||||
Reference in New Issue
Block a user