From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Janning Vygen <vygen@kicktipp.de>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: slow pg_dump with bytea
Date: Fri, 20 Oct 2023 14:51:30 +0200
Message-ID: <b425b90d7f8ecf0b5cf32b7dbba720e548508e81.camel@cybertec.at> (raw)
In-Reply-To: <1c4abe5d-d6ca-4176-9692-2e95ce945438@kicktipp.de>
References: <1325559b-6a40-411d-a1ab-1e1162e3722b@kicktipp.de>
<cb80c6f3c21a798d29f7db46c78e650bbcd95705.camel@cybertec.at>
<1c4abe5d-d6ca-4176-9692-2e95ce945438@kicktipp.de>
On Fri, 2023-10-20 at 14:08 +0200, Janning Vygen wrote:
> Anyhow, for me it seems odd that you can dump in a fraction of time
> compared to the default settings. With the solution in the link you have
> both: speed and compression. Which seems to be offered by pg_dump -Z
> option too, acording to the level yu set. But it isn't.
Who says that the only goal of pg_dump is speed?
Like I said, specialized compression software is way better than PostgreSQL's
built-in "pglz".
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, vygen@kicktipp.de, pgsql-bugs@lists.postgresql.org
Subject: Re: slow pg_dump with bytea
In-Reply-To: <b425b90d7f8ecf0b5cf32b7dbba720e548508e81.camel@cybertec.at>
* 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