pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedReference Guide diffs
3+ messages / 3 participants
[nested] [flat]
* Reference Guide diffs
@ 2001-03-05 17:09 Pierce Tyler <pierce@greatbridge.com>
0 siblings, 1 reply; 3+ messages in thread
From: Pierce Tyler @ 2001-03-05 17:09 UTC (permalink / raw)
To: lockhart@fourpalms.org; pgsql-docs
I'm attaching several minor diffs (mostly typos) that impact the
Reference Guide.
Pierce
--
--------------------------------------------------------------
Pierce Tyler | e: pierce@greatbridge.com
Technical Writer | p: (757)233-5544
Great Bridge, LLC | w: www.greatbridge.com
www.greatbridge.org
Attachments: download all (8 files, .tar.gz)
alter_table.sgml.diff (text/plain, 588B) download
*** ref-symlink/alter_table.sgml Sat Feb 10 11:41:30 2001
--- alter_table.sgml Mon Mar 5 09:38:56 2001
***************
*** 107,113 ****
<term><replaceable class="PARAMETER">New user </replaceable></term>
<listitem>
<para>
! The userid of the new owner of the table.
</para>
</listitem>
</varlistentry>
--- 107,113 ----
<term><replaceable class="PARAMETER">New user </replaceable></term>
<listitem>
<para>
! The user name of the new owner of the table.
</para>
</listitem>
</varlistentry>
comment.sgml.diff (text/plain, 875B) download
*** ref-symlink/comment.sgml Sat Jan 20 15:59:29 2001
--- comment.sgml Mon Mar 5 09:42:41 2001
***************
*** 101,107 ****
<para>
<command>COMMENT</command> adds a comment to an object that can be
easily retrieved with <application>psql's</application>
! <emphasis>\dd</emphasis> or <emphasis>\d+</emphasis> commands.
To remove a comment, use <literal>NULL</literal>.
Comments are automatically dropped when the object is dropped.
</para>
--- 101,107 ----
<para>
<command>COMMENT</command> adds a comment to an object that can be
easily retrieved with <application>psql's</application>
! <emphasis>\dd</emphasis>, <emphasis>\d+</emphasis>, or <emphasis>\l+</emphasis>commands.
To remove a comment, use <literal>NULL</literal>.
Comments are automatically dropped when the object is dropped.
</para>
create_type.sgml.diff (text/plain, 892B) download
*** ref-symlink/create_type.sgml Sat Jan 13 18:58:55 2001
--- create_type.sgml Mon Mar 5 10:01:53 2001
***************
*** 298,304 ****
<para>
The <replaceable class="parameter">storage</replaceable> keyword
! allows selection of TOAST storage method for variable-length data types
(only <literal>plain</literal> is allowed for fixed-length types).
<literal>plain</literal> disables TOAST for the data type: it will always
be stored in-line and not compressed.
--- 298,304 ----
<para>
The <replaceable class="parameter">storage</replaceable> keyword
! allows selection of The Oversized-Attribute Storage Technique (TOAST) for variable-length data types
(only <literal>plain</literal> is allowed for fixed-length types).
<literal>plain</literal> disables TOAST for the data type: it will always
be stored in-line and not compressed.
pg_config-ref.sgml.diff (text/html, 892B) download
*** ref-symlink/pg_config-ref.sgml Sat Nov 11 18:01:45 2000
--- pg_config-ref.sgml Mon Mar 5 10:42:25 2001
***************
*** 32,38 ****
<refsect1>
<title>Description</>
<para>
! The <application>pg_config</> stores and provides configuration parameters
of the currently installed version of <productname>PostgreSQL</>. It is
intended, for example, to be used by software packages that want to interface
to <productname>PostgreSQL</> in order to find the respective header files
--- 32,38 ----
<refsect1>
<title>Description</>
<para>
! The <application>pg_config</> utility provides configuration parameters
of the currently installed version of <productname>PostgreSQL</>. It is
intended, for example, to be used by software packages that want to interface
to <productname>PostgreSQL</> in order to find the respective header files
pg_dump.sgml.diff (text/plain, 505B) download
[ptyler@greatbridge_dev1 mar5]$ diff -c ref-symlink/pg_dump.sgml pg_dump.sgml
*** ref-symlink/pg_dump.sgml Mon Dec 25 18:15:26 2000
--- pg_dump.sgml Fri Mar 2 17:28:50 2001
***************
*** 78,84 ****
<term>-b</term>
<listitem>
<para>
! Dump BLOB data.
</para>
</listitem>
</varlistentry>
--- 78,84 ----
<term>-b</term>
<listitem>
<para>
! Dump data and BLOB data.
</para>
</listitem>
</varlistentry>
pg_dumpall.sgml.diff (text/plain, 1.4K) download
*** ref-symlink/pg_dumpall.sgml Sat Feb 10 20:41:00 2001
--- pg_dumpall.sgml Mon Mar 5 09:25:48 2001
***************
*** 55,61 ****
Since <application>pg_dumpall</application> reads tables from all
databases you will most likely have to connect as a database
superuser in order to produce a complete dump. Also you will need
! superuser priviledges to execute the saves script in order to be
allowed to add users and groups, and to create databases.
</para>
--- 55,61 ----
Since <application>pg_dumpall</application> reads tables from all
databases you will most likely have to connect as a database
superuser in order to produce a complete dump. Also you will need
! superuser privileges to execute the saved script in order to be
allowed to add users and groups, and to create databases.
</para>
***************
*** 146,152 ****
(It is not important to which database you connect here since the
script file created by <application>pg_dumpall</application> will
contain the appropriate commands to create and connect to the saved
! databases.
</para>
</refsect1>
--- 146,152 ----
(It is not important to which database you connect here since the
script file created by <application>pg_dumpall</application> will
contain the appropriate commands to create and connect to the saved
! databases.)
</para>
</refsect1>
pg_restore.sgml.diff (text/plain, 1.3K) download
*** ref-symlink/pg_restore.sgml Mon Dec 25 18:15:26 2000
--- pg_restore.sgml Mon Mar 5 09:31:43 2001
***************
*** 428,440 ****
The most flexible output file format is the new 'custom' format (-Fc).
It allows for
selection and reordering of all archived items, and is compressed by de
fault. The TAR
format (-Ft) is not compressed and it is not possible to reorder
! data load, but it is otherwise quite flexible.
</para>
<para>
To reorder the items, it is first necessary to dump the contents of the
archive:
<programlisting>
! $ pg_restore acrhive.file --list > archive.lis
</programlisting>
This file consists of a header and one line for each item, eg.
<programlisting>
--- 428,440 ----
The most flexible output file format is the new 'custom' format (-Fc).
It allows for
selection and reordering of all archived items, and is compressed by de
fault. The TAR
format (-Ft) is not compressed and it is not possible to reorder
! data when loading, but it is otherwise quite flexible.
</para>
<para>
To reorder the items, it is first necessary to dump the contents of the
archive:
<programlisting>
! $ pg_restore archive.file --list > archive.lis
</programlisting>
This file consists of a header and one line for each item, eg.
<programlisting>
set.sgml.diff (text/plain, 740B) download
*** ref-symlink/set.sgml Thu Oct 5 15:48:19 2000
--- set.sgml Mon Mar 5 10:09:36 2001
***************
*** 196,202 ****
The value for the seed to be used by the
<function>random</function> function. Allowed
values are floating point numbers between 0 and 1, which
! are then multiplied by 2^31-1. This product will
silently overflow if a number outside the range is used.
</para>
--- 196,202 ----
The value for the seed to be used by the
<function>random</function> function. Allowed
values are floating point numbers between 0 and 1, which
! are then multiplied by RAND_MAX. This product will
silently overflow if a number outside the range is used.
</para>
* Re: Reference Guide diffs
@ 2001-03-05 19:12 Peter Eisentraut <peter_e@gmx.net>
parent: Pierce Tyler <pierce@greatbridge.com>
0 siblings, 1 reply; 3+ messages in thread
From: Peter Eisentraut @ 2001-03-05 19:12 UTC (permalink / raw)
To: Pierce Tyler <pierce@greatbridge.com>; +Cc: pgsql-docs
Pierce Tyler writes:
> I'm attaching several minor diffs (mostly typos) that impact the
> Reference Guide.
> ! allows selection of TOAST storage method for variable-length data types
> ! allows selection of The Oversized-Attribute Storage Technique (TOAST) for variable-length data types
This is a bit tacky. Let's not go there.
--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Reference Guide diffs
@ 2001-03-05 20:45 Tom Lane <tgl@sss.pgh.pa.us>
parent: Peter Eisentraut <peter_e@gmx.net>
0 siblings, 0 replies; 3+ messages in thread
From: Tom Lane @ 2001-03-05 20:45 UTC (permalink / raw)
To: Peter Eisentraut <peter_e@gmx.net>; +Cc: Pierce Tyler <pierce@greatbridge.com>; pgsql-docs
Peter Eisentraut <peter_e@gmx.net> writes:
> Pierce Tyler writes:
>> ! allows selection of TOAST storage method for variable-length data types
>> ! allows selection of The Oversized-Attribute Storage Technique (TOAST) for variable-length data types
> This is a bit tacky. Let's not go there.
I agree with Peter on this one ...
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2001-03-05 20:45 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-03-05 17:09 Reference Guide diffs Pierce Tyler <pierce@greatbridge.com>
2001-03-05 19:12 ` Peter Eisentraut <peter_e@gmx.net>
2001-03-05 20:45 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox