Re: Migration study, step 1: bulk write performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Cc: Ron <rjpeace(at)earthlink(dot)net>, Mikael Carneholm <Mikael(dot)Carneholm(at)WirelessCar(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Migration study, step 1: bulk write performance
Date: 2006-03-21 21:56:25
Message-ID: 2262.1142978185@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Scott Marlowe <smarlowe(at)g2switchworks(dot)com> writes:
> I've also found that modest increases in commit_siblings and
> commit_delay help a lot on certain types of imports.

On a data import? Those really should have zero effect on a
single-process workload. Or are you doing multiple concurrent imports?

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2006-03-21 22:23:14 Re: Migration study, step 1: bulk write performance
Previous Message Alvaro Herrera 2006-03-21 21:20:38 Re: Migration study, step 1: bulk write performance