From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Janning Vygen <vygen@kicktipp.de>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: slow pg_dump with bytea
Date: Fri, 20 Oct 2023 15:18:19 +0200
Message-ID: <202310201318.ukcklynpe5bq@alvherre.pgsql> (raw)
In-Reply-To: <1325559b-6a40-411d-a1ab-1e1162e3722b@kicktipp.de>
On 2023-Oct-20, Janning Vygen wrote:
> So maybe you can fix it by changing the pg_dump process to not compress any
> bytea data.
The problem with this idea is that the compression applies to the whole
data stream. The backup format doesn't allow to compress some columns
and not others. Doing that would require a lot of changes to pg_dump.
Maybe a workable idea would be to allow excluding individual tables from
being compressed.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)
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-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, vygen@kicktipp.de, pgsql-bugs@lists.postgresql.org
Subject: Re: slow pg_dump with bytea
In-Reply-To: <202310201318.ukcklynpe5bq@alvherre.pgsql>
* 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