Re: performance of insert/delete/update

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
Cc: Wei Weng <wweng(at)kencast(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: performance of insert/delete/update
Date: 2002-11-25 22:33:07
Message-ID: 200211251433.07049.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Scott,

> It's quite easy to test if you have a database with a large table to play
> with, use pg_dump to dump a table with the -d switch (makes the dump use
> insert statements.) Then, make two versions of the dump, one which has a
> begin;end; pair around all the inserts and one that doesn't, then use psql
> -e to restore both dumps. The difference is HUGE. Around 10 to 20 times
> faster with the begin end pairs.
>
> I'd think that anyone who's used postgresql for more than a few months
> could corroborate my experience.

Ouch!

No need to get testy about it.

Your test works as you said; the way I tried testing it before was different.
Good to know. However, this approach is only useful if you are doing
rapidfire updates or inserts coming off a single connection. But then it is
*very* useful.

--
-Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message scott.marlowe 2002-11-25 22:59:16 Re: performance of insert/delete/update
Previous Message scott.marlowe 2002-11-25 22:24:42 Re: Solaris still failing RC2

Browse pgsql-performance by date

  From Date Subject
Next Message scott.marlowe 2002-11-25 22:59:16 Re: performance of insert/delete/update
Previous Message scott.marlowe 2002-11-25 16:31:20 Re: performance of insert/delete/update