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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: PostgreSQL 8.4 performance tuning questions


  • From: Scott Carey <scott(at)richrelevance(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Matthew Wakeling <matthew(at)flymine(dot)org>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
  • Subject: Re: PostgreSQL 8.4 performance tuning questions
  • Date: Thu, 30 Jul 2009 13:19:58 -0700
  • Message-id: <C6974E7E.DD80%scott@richrelevance.com> <text/plain>

On 7/30/09 1:15 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Scott Carey <scott(at)richrelevance(dot)com> writes:
>> Dump needs to be parallelized or at least pipelined to use more cores.  COPY
>> on one thread, compression on another?
> 
> We already do that (since compression happens on the pg_dump side).
> 
>                         regards, tom lane
> 

Well, that isn't what I meant.  pg_dump uses CPU outside of compression
doing various things, If that Cpu is 10% as much as the compression, then
splitting them up would yield ~10% gain when CPU bound. 




Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group