Re: Parallel pg_restore versus old dump files

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Igor Neyman <ineyman(at)perceptron(dot)com>
Subject: Re: Parallel pg_restore versus old dump files
Date: 2010-06-23 09:37:28
Message-ID: AANLkTilUuDdynIcJFqUeH96RooV_h0VIYsCTAYL8yBKF@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 23, 2010 at 03:26, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>> 4. Is there any value in back-porting the Windows FSEEKO support into
>>> 8.3 and 8.2?  Arguably, not writing the data offsets is a performance
>>> bug.  However a back-port won't do anything for people who are dumping
>>> with less than the latest minor release of pg_dump, so doing this might
>>> be largely wasted effort.
>
>> I doubt it's worth it, but I could be persuaded otherwise.
>
> I'm leaning in that direction too.  Anybody who's doing a version
> upgrade really ought to be using the newer pg_dump version anyway ...

+1 on not backpatching that stuff - it's build system related, so it's
kind of fragile on the windows side :-)

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2010-06-23 10:20:23 Re: Parallel pg_restore versus old dump files
Previous Message Sander, Ingo (NSN - DE/Munich) 2010-06-23 08:48:01 Streaming Replication: sql error on standby