pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <jnasby@pervasive.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: mario.splivalo@mobart.hr
Cc: pgsql-admin@postgresql.org
Subject: Re: archive_log command...
Date: Tue, 27 Jun 2006 19:17:46 -0500
Message-ID: <DF27B15B-97EF-4E8D-807A-FDFE9591507B@pervasive.com> (raw)
In-Reply-To: <200606230542.k5N5gJG12667@momjian.us>
References: <200606230542.k5N5gJG12667@momjian.us>

On Jun 23, 2006, at 12:42 AM, Bruce Momjian wrote:
> Mario Splivalo wrote:
>> On Wed, 2006-06-21 at 21:30 -0400, Bruce Momjian wrote:
>>> Mario Splivalo wrote:
>>>> Can I force archiving of the WAL files using CHECKPOINT  
>>>> statement? My
>>>> checkpoing_segments is set to 32, but still archive_command is  
>>>> beeing
>>>> called up only every 45 minutes or so. Is there a way to speed  
>>>> this up a
>>>> bit? (I'd love to have it around 10 minutes, so I can have  
>>>> almost-live
>>>> backed-up server).
>>>
>>> No, but it is on the TODO list.
>>>
>>
>> So, the only thing I could to is to reduce checkpoint_segments?
>
> No, that doesn't help because a partially-filled WAL file with little
> database activity could be stay unarchived for a long time.

You can however copy the active WAL file at any time, and as many  
times as you want. And there's recently been a function added that  
will tell you what that exact file is (I think it's only in HEAD, but  
I could be wrong).
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (5+ messages)

Message-ID: <DF27B15B-97EF-4E8D-807A-FDFE9591507B@pervasive.com>
Permalink:  ../DF27B15B-97EF-4E8D-807A-FDFE9591507B@pervasive.com/
Also on:    postgresql.org/message-id/DF27B15B-97EF-4E8D-807A-FDFE9591507B@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, bruce@momjian.us, mario.splivalo@mobart.hr
  Subject: Re: archive_log command...
  In-Reply-To: <DF27B15B-97EF-4E8D-807A-FDFE9591507B@pervasive.com>
  References: <200606230542.k5N5gJG12667@momjian.us> <DF27B15B-97EF-4E8D-807A-FDFE9591507B@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox