1
0
mirror of https://github.com/postgres/postgres.git synced 2025-06-13 07:41:39 +03:00

For consistency with the rest of PostgreSQL, rename BLOBs to large objects

in messages and documentation.
This commit is contained in:
Peter Eisentraut
2001-09-21 21:58:30 +00:00
parent 196700c372
commit fdf07fe14f
8 changed files with 56 additions and 56 deletions

View File

@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.36 2001/09/03 12:57:50 petere Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.37 2001/09/21 21:58:29 petere Exp $
Postgres documentation
-->
@ -144,7 +144,7 @@ Postgres documentation
<term>--blobs</term>
<listitem>
<para>
Dump data and <acronym>BLOB</acronym> data.
Include large objects in dump.
</para>
</listitem>
</varlistentry>
@ -616,8 +616,8 @@ connectDBStart() -- connect() failed: No such file or directory
</para>
<para>
To dump a database called mydb that contains
<acronym>BLOB</acronym>s to a <filename>tar</filename> file:
To dump a database called <literal>mydb</> that contains
large objects to a <filename>tar</filename> file:
<screen>
<prompt>$</prompt> <userinput>pg_dump -Ft -b mydb &gt; db.tar</userinput>
@ -625,8 +625,8 @@ connectDBStart() -- connect() failed: No such file or directory
</para>
<para>
To reload this database (with <acronym>BLOB</acronym>s) to an
existing database called newdb:
To reload this database (with large objects) to an
existing database called <literal>newdb</>:
<screen>
<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput>

View File

@ -1,4 +1,4 @@
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.17 2001/09/21 21:58:30 petere Exp $ -->
<refentry id="APP-PGRESTORE">
<docinfo>
@ -213,7 +213,7 @@
<listitem>
<para>
Connect to database <replaceable class="parameter">dbname</replaceable> and restore
directly into the database. BLOBs can only be restored by using a direct database connection.
directly into the database. Large objects can only be restored by using a direct database connection.
</para>
</listitem>
</varlistentry>
@ -585,8 +585,8 @@ connectDBStart() -- connect() failed: No such file or directory
<listitem>
<para>
<command>pg_restore</command> will not restore BLOBs for a single table. If
an archive contains BLOBs, then all BLOBs will be restored.
<command>pg_restore</command> will not restore large objects for a single table. If
an archive contains large objects, then all large objects will be restored.
</para>
</listitem>
@ -620,8 +620,8 @@ connectDBStart() -- connect() failed: No such file or directory
</para>
<para>
To dump a database called mydb that contains
<acronym>BLOB</acronym>s to a <filename>tar</filename> file:
To dump a database called <literal>mydb</> that contains
large objects to a <filename>tar</filename> file:
<screen>
<prompt>$</prompt> <userinput>pg_dump -Ft -b mydb &gt; db.tar</userinput>
@ -629,8 +629,8 @@ connectDBStart() -- connect() failed: No such file or directory
</para>
<para>
To reload this database (with <acronym>BLOB</acronym>s) to an
existing database called newdb:
To reload this database (with large objects) to an
existing database called <literal>newdb</>:
<screen>
<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput>