From: Nathan Bossart <nathandbossart@gmail.com>
To: Euler Taveira <euler@eulerto.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: improve performance of pg_dump with many sequences
Date: Thu, 11 Jul 2024 21:09:17 -0500
Message-ID: <ZpCQTZtXL85P5SaT@nathan> (raw)
In-Reply-To: <d7f5942e-00ba-4d90-9bac-f0b2b7092dc4@app.fastmail.com>
References: <20240503025140.GA1227404@nathanxps13>
<Zo2LdwUamOq6HzIU@nathan>
<0a0f4d52-ab75-4d69-abe8-5713bf70eee6@app.fastmail.com>
<Zo8Fl53vBVS1Cnmt@nathan>
<d7f5942e-00ba-4d90-9bac-f0b2b7092dc4@app.fastmail.com>
On Wed, Jul 10, 2024 at 11:52:33PM -0300, Euler Taveira wrote:
> On Wed, Jul 10, 2024, at 7:05 PM, Nathan Bossart wrote:
>> Unfortunately, I think we have to keep this workaround since older minor
>> releases of PostgreSQL don't have the fix.
>
> Hmm. Right.
On second thought, maybe we should just limit this improvement to the minor
releases with the fix so that we _can_ get rid of the workaround. Or we
could use the hacky workaround only for versions with the bug.
--
nathan
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-hackers@postgresql.org
Cc: nathandbossart@gmail.com, euler@eulerto.com
Subject: Re: improve performance of pg_dump with many sequences
In-Reply-To: <ZpCQTZtXL85P5SaT@nathan>
* 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