Skip site navigation (1) Skip section navigation (2)

Re: NOLOGGING option, or ?

From: Jochem van Dieten <jochemd(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: NOLOGGING option, or ?
Date: 2005-06-01 14:07:37
Message-ID: f96a9b8305060107074de65307@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 01 Jun 2005 04:44:24 -0400, Greg Stark wrote:
> Greg Stark writes:
>> 
>> For CREATE TABLE AS in the non-PITR case you don't really need to WAL log the
>> records at all. If it fails in the middle you just drop the table. When it
>> completes you do a checkpoint before acknowledging the COMMIT.
>>
>> I think this is already done for CREATE INDEX/REINDEX, also only in the
>> non-PITR case.

Checkpoint or fsync?


> Sorry to followup to my own message, but it occurs to me that COPY could be
> made to automatically do this for the case of an empty destination table too.

Why only on an empty table? What is the problem with bypassing WAL on
any table as long as all files of that table are fsync'ed before
commit?


> Again this sadly only works in the non-PITR case.

Apart from that problem of course :)

Jochem

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-06-01 14:12:18
Subject: Re: NOLOGGING option, or ?
Previous:From: Tom LaneDate: 2005-06-01 14:07:36
Subject: Re: Cost of XLogInsert CRC calculations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group