public inbox for [email protected]
help / color / mirror / Atom feedFrom: Pierre Ducroquet <[email protected]>
To: Nathan Bossart <[email protected]>
Cc: [email protected]
Subject: Re: Improvements in pg_dump/pg_restore toc format and performances
Date: Tue, 19 Sep 2023 10:25:09 +0200
Message-ID: <1867814.CQOukoFCf9@peanuts2> (raw)
In-Reply-To: <20230918215442.GB2661288@nathanxps13>
References: <2656000.KRxA6XjA2N@peanuts2>
<20230918215247.GA2661288@nathanxps13>
<20230918215442.GB2661288@nathanxps13>
On Monday, September 18, 2023 11:54:42 PM CEST Nathan Bossart wrote:
> On Mon, Sep 18, 2023 at 02:52:47PM -0700, Nathan Bossart wrote:
> > On Thu, Jul 27, 2023 at 10:51:11AM +0200, Pierre Ducroquet wrote:
> >> I ended up writing several patches that shaved some time for pg_restore
> >> -l,
> >> and reduced the toc.dat size.
> >
> > I've only just started taking a look at these patches, and I intend to do
> > a
> > more thorough review in the hopefully-not-too-distant future.
>
> Since cfbot is failing on some pg_upgrade and pg_dump tests, I've set this
> to waiting-on-author.
FYI, the failures are related to patch 0004, I said it was dirty, but it was
apparently an understatement. Patches 0001 to 0003 don't exhibit any
regression.
view thread (6+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Improvements in pg_dump/pg_restore toc format and performances
In-Reply-To: <1867814.CQOukoFCf9@peanuts2>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox