pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: William Yu <wyu@talisys.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Disabling WAL for bulk data loads
Date: Wed, 14 Sep 2005 13:58:14 -0400
Message-ID: <6159.1126720694@sss.pgh.pa.us> (raw)
In-Reply-To: <dg9k7p$2e7d$1@news.hub.org>
References: <BAY108-F115459FF84EB8232582111B9980@phx.gbl>
	<dg9k7p$2e7d$1@news.hub.org>

William Yu <wyu@talisys.com> writes:
> If you have enough memory, you can always make a ramdisk to store the 
> WAL temporarily while you bulk load data. I also temporarily alter the 
> config to set checkpoint_segments = 1 to use as few pg_xlog files as 
> possible.

Really?  That seems pretty counterproductive to me.  I've never seen
a case where reducing checkpoint_segments increased performance.
Checkpoints are expensive, and usually you want 'em far apart.

			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <6159.1126720694@sss.pgh.pa.us>
Permalink:  ../6159.1126720694@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6159.1126720694@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, wyu@talisys.com
  Subject: Re: Disabling WAL for bulk data loads
  In-Reply-To: <6159.1126720694@sss.pgh.pa.us>
  References: <BAY108-F115459FF84EB8232582111B9980@phx.gbl> <dg9k7p$2e7d$1@news.hub.org> <6159.1126720694@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox