Re: avoiding WAL logging in 8.3

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: "Tatsuo Ishii" <ishii(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: avoiding WAL logging in 8.3
Date: 2007-07-24 16:59:22
Message-ID: 25A5D521-560A-40E6-BEDD-E91B3C9F1DED@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 23, 2007, at 11:30 PM, Simon Riggs wrote:
> On Tue, 2007-07-24 at 13:04 +0900, Tatsuo Ishii wrote:
>
>> I noticed in 8.3 there are chances where we can avoid WAL logging.
>> For
>> example, 8.3's pgbench was modified to use TRUNCATE right before
>> COPY. Is there any documentation which describes that kind of
>> techniques? If there's none, I would volunteer the work to create
>> such
>> a documentation since I think this is valuable information for DBAs
>> who wish to migrate to 8.3.
>
> The Performance Tips section has been modified to describe this. Would
> you like me to add something elsewhere also? Multiple entry points to
> information helps everybody, so I'll happily add more.

I would mention it in the documentation for each affected command
(COPY, TRUNCATE, etc). I suspect a lot of folks end up only using the
SQL reference section.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-07-24 17:09:06 Re: strange buildfarm failure on lionfish
Previous Message Gregory Stark 2007-07-24 16:53:02 Re: strange buildfarm failure on lionfish