| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Holger Jakobs <holger(at)jakobs(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, Ron Watkins <rwatki(at)gmail(dot)com> |
| Subject: | Re: Postgres question |
| Date: | 2020-11-09 16:41:15 |
| Message-ID: | 554a89ce48ca66dab98296266da83a74cfe94241.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 2020-11-06 at 17:13 -0500, Tom Lane wrote:
> Holger Jakobs <holger(at)jakobs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Creston Jamison | 2020-11-09 16:43:01 | Autovacuum Truncation Phase Loop? |
| Previous Message | Raj kumar | 2020-11-09 14:53:09 | ERROR: found xmin 10843132 from before relfrozenxid15785806 during vacuum on JSONB TOAST TABLE |