Skip site navigation (1) Skip section navigation (2)

Re: pg_dump additional options for performance

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump additional options for performance
Date: 2008-02-26 18:44:44
Message-ID: 20080226104444.4138b2c5@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 26 Feb 2008 10:32:59 -0800
Jeff Davis <pgsql(at)j-davis(dot)com> wrote:

> On Tue, 2008-02-26 at 17:16 +0000, Simon Riggs wrote:
> > I've not been advocating improving pg_restore, which is where the
> > -Fc tricks come in.
> 
> Oh, then it was a miscommunication on my part, because I was talking
> about pg_restore, and I assumed you were as well.
> 

IMO the place to start is COPY which is per my tests, slow. Multi
worker connection restore is great and I have proven that with some
work it can provide o.k. results but it is certainly not acceptable.

Let's not fix the middle and ignore the beginning.

Sincerely,

Joshua D. Drake



- -- 
The PostgreSQL Company since 1997: http://www.commandprompt.com/ 
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director |  PostgreSQL political pundit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHxF4fATb/zqfZUUQRAty+AJ0VmYoY1wZ+Sijb/eRiDL+LedKrHgCfZuIn
SQTgRqm14gVfubz3u3o54mc=
=uIYl
-----END PGP SIGNATURE-----

In response to

Responses

pgsql-hackers by date

Next:From: Neil ConwayDate: 2008-02-26 18:54:02
Subject: Re: code cleanup of timestamp code
Previous:From: Robert LorDate: 2008-02-26 18:44:16
Subject: Re: Proposed changes to DTrace probe implementation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group