Re: Database restore speed

From: David Lang <dlang(at)invendra(dot)net>
To: Michael Stone <mstone+postgres(at)mathom(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Database restore speed
Date: 2005-12-03 09:12:07
Message-ID: Pine.LNX.4.62.0512030109570.2807@qnivq.ynat.uz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, 2 Dec 2005, Michael Stone wrote:

> On Fri, Dec 02, 2005 at 01:24:31PM -0800, Luke Lonergan wrote:
>> From a performance standpoint no argument, although you're betting that you
>> can do parsing / conversion faster than the COPY core in the backend can
>
> Not necessarily; you may be betting that it's more *efficient* to do the
> parsing on a bunch of lightly loaded clients than your server. Even if
> you're using the same code this may be a big win.

it's a lot easier to throw hardware at the problem by spliting your
incomeing data between multiple machines and have them all working in
parallel throwing the data at one database then it is to throw more
hardware at the database server to speed it up (and yes, assuming that MPP
splits the parseing costs as well, it can be an answer for some types of
systems)

David Lang

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message David Lang 2005-12-03 09:22:04 Re: Database restore speed
Previous Message David Lang 2005-12-03 09:07:15 Re: Database restore speed