Message-ID: <554a89ce48ca66dab98296266da83a74cfe94241.camel@cybertec.at>
Subject: Re: Postgres question
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tom Lane <tgl@sss.pgh.pa.us>, Holger Jakobs <holger@jakobs.com>
Cc: pgsql-admin@lists.postgresql.org, Ron Watkins <rwatki@gmail.com>
Date: Mon, 09 Nov 2020 17:41:15 +0100
In-Reply-To: <1662015.1604700817@sss.pgh.pa.us>
References: 
	<CAPdrarq+tNYUJMPTPfTwQhXphv7+Yxme6E2+iRnv9z595zetpg@mail.gmail.com>
	 <5a135ef0-b970-9a69-f721-6c8b825755ba@jakobs.com>
	 <1662015.1604700817@sss.pgh.pa.us>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 2020-11-06 at 17:13 -0500, Tom Lane wrote:
> 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.

The exception is when except when --schema, --table, or --schema-only
is specified.  Then you have to use --blobs to get the large objects
in the dump.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com