| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Luke Lonergan <llonergan(at)greenplum(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 8.3 / 8.2.6 restore comparison |
| Date: | 2008-02-26 05:18:57 |
| Message-ID: | 20080225211857.0db12f74@jd-laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 25 Feb 2008 14:11:16 -0800
"Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
O.k. with 24 connections 3.5 hours. Testing with 12 now. 6 never
finished due to a bug.
Observations:
As simple as this solution is, it is not eloquent nor is it smart.
Using this method, if you have a 100GB table (which is very common)
you are still bound in a bad way by a single connection and you are
holding up everyone else.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-26 05:39:29 | Re: pg_dump additional options for performance |
| Previous Message | Tom Lane | 2008-02-26 02:59:48 | Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the |