database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

pg_dump: Remove "blob" terminology

Browse Source 
For historical reasons, pg_dump refers to large objects as "BLOBs".
This term is not used anywhere else in PostgreSQL, and it also means
something different in the SQL standard and other SQL systems.

This patch renames internal functions, code comments, documentation,
etc. to use the "large object" or "LO" terminology instead.  There is
no functionality change, so the archive format still uses the name
"BLOB" for the archive entry.  Additional long command-line options
are added with the new naming.

Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
Discussion: https://www.postgresql.org/message-id/flat/868a381f-4650-9460-1726-1ffd39a270b4%40enterprisedb.com
This commit is contained in:
Peter Eisentraut
2022-12-05 08:52:11 +01:00
parent 8a476fda5e
commit 35ce24c333
14 changed files with 367 additions and 361 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/src/sgml/ref/pg_dump.sgml
View File

@ -132,7 +132,8 @@ PostgreSQL documentation
<varlistentry>
<term><option>-b</option></term>
<term><option>--blobs</option></term>
<term><option>--large-objects</option></term>
<term><option>--blobs</option> (deprecated)</term>
<listitem>
<para>
Include large objects in the dump. This is the default behavior
@ -140,7 +141,7 @@ PostgreSQL documentation
<option>--schema-only</option> is specified. The <option>-b</option>
switch is therefore only useful to add large objects to dumps
where a specific schema or table has been requested. Note that
blobs are considered data and therefore will be included when
large objects are considered data and therefore will be included when
<option>--data-only</option> is used, but not
when <option>--schema-only</option> is.
</para>
@ -149,7 +150,8 @@ PostgreSQL documentation
<varlistentry>
<term><option>-B</option></term>
<term><option>--no-blobs</option></term>
<term><option>--no-large-objects</option></term>
<term><option>--no-blobs</option> (deprecated)</term>
<listitem>
<para>
Exclude large objects in the dump.
@ -323,7 +325,7 @@ PostgreSQL documentation
<para>
Output a directory-format archive suitable for input into
<application>pg_restore</application>. This will create a directory
with one file for each table and blob being dumped, plus a
with one file for each table and large object being dumped, plus a
so-called Table of Contents file describing the dumped objects in a
machine-readable format that <application>pg_restore</application>
can read. A directory format archive can be manipulated with
@ -434,9 +436,9 @@ PostgreSQL documentation
<note>
<para>
Non-schema objects such as blobs are not dumped when <option>-n</option> is
specified. You can add blobs back to the dump with the
<option>--blobs</option> switch.
Non-schema objects such as large objects are not dumped when <option>-n</option> is
specified. You can add large objects back to the dump with the
<option>--large-objects</option> switch.
</para>
</note>