From: Tom Lane <tgl@sss.pgh.pa.us>
To: Holger Jakobs <holger@jakobs.com>
Cc: pgsql-admin@lists.postgresql.org, Ron Watkins <rwatki@gmail.com>
Subject: Re: Postgres question
Date: Fri, 06 Nov 2020 17:13:37 -0500
Message-ID: <1662015.1604700817@sss.pgh.pa.us> (raw)
In-Reply-To: <5a135ef0-b970-9a69-f721-6c8b825755ba@jakobs.com>
References: <CAPdrarq+tNYUJMPTPfTwQhXphv7+Yxme6E2+iRnv9z595zetpg@mail.gmail.com>
<5a135ef0-b970-9a69-f721-6c8b825755ba@jakobs.com>
Holger Jakobs <holger@jakobs.com> writes:
> Of course pg_dump can also dump blobs, and it's even the default. You
> may use the option --no-blobs to leave them out.
> A glance at the man page can be more informative than just hearing
> something from someone.
Especially information as out of date as that :-(. Glancing at the
commit log, the very first version of pg_dump (in PG 7.0) did not do
blobs, but that was fixed by 7.1. I have a vague recollection that
--no-blobs might've been the default for a while after that, but
certainly it's been well over a decade since it wasn't default.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, holger@jakobs.com, rwatki@gmail.com
Subject: Re: Postgres question
In-Reply-To: <1662015.1604700817@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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