Re: Disabling WAL for bulk data loads

From: William Yu <wyu(at)talisys(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Disabling WAL for bulk data loads
Date: 2005-09-14 18:01:11
Message-ID: 43286567.6040204@talisys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Tom Lane wrote:
> William Yu <wyu(at)talisys(dot)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.

Just poor grammar on my part. I meant decreasing checkpoint_segments
when using a ramdisk for WAL in order to keep Postgres from croaking on
lack of disk space for pg_xlog.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Lane Van Ingen 2005-09-14 22:23:18 FW: Server Time Setting
Previous Message Tom Lane 2005-09-14 17:58:14 Re: Disabling WAL for bulk data loads