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

Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset
Date: 2010-03-08 13:26:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Thu, Feb 25, 2010 at 7:48 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, Feb 25, 2010 at 7:22 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Yeah. The current pg_*_last_location() functions don't cut it though,
>> you need to retain logs back to the redo location of the last
>> restartpoint. That's what %r returns. Maybe we should add another function?
> +1

The attached patch introduces new function 'pg_last_checkpoint_start_location'
(better name?) that reports the XLOG location where the last checkpoint or
restartpoint started (i.e., the REDO starting location). This would be useful
to truncate the archived files to just the minimum required for recovery.

Is it worth applying this patch?


Fujii Masao
NTT Open Source Software Center

Attachment: last_ckpt_start_location_v1.patch
Description: text/x-patch (4.4 KB)

In response to

pgsql-hackers by date

Next:From: Tim BunceDate: 2010-03-08 14:37:20
Subject: Re: Safe security
Previous:From: Michael MeskesDate: 2010-03-08 12:15:10
Subject: Re: ecpg compiler warning about char* comparison

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