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

New XLOG record indicating WAL-skipping

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: New XLOG record indicating WAL-skipping
Date: 2010-01-05 06:55:38
Message-ID: 3f0b79eb1001042255t26fd1015n5218852e32b7279b@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Dec 9, 2009 at 6:25 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Here is the patch:
>
> - Write an XLOG UNLOGGED record in WAL if WAL-logging is skipped for only
>  the reason that WAL archiving is not enabled and such record has not been
>  written yet.
>
> - Cause archive recovery to end if an XLOG UNLOGGED record is found during
>  it.

Here's an updated version of my "New XLOG record indicating WAL-skipping" patch.
http://archives.postgresql.org/pgsql-hackers/2009-12/msg00788.php

This is rebased to CVS HEAD.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment: log_unlogged_op_0105.patch
Description: text/x-patch (7.2 KB)

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-01-05 08:09:47
Subject: Somebody has broken autovacuum's abort path
Previous:From: black lightDate: 2010-01-05 05:56:48
Subject: execute sql commands in core

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