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

Re: archive_log command...

From: Jim Nasby <jnasby(at)pervasive(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: mario(dot)splivalo(at)mobart(dot)hr, pgsql-admin(at)postgresql(dot)org
Subject: Re: archive_log command...
Date: 2006-06-28 00:17:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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(at)pervasive(dot)com
Pervasive Software    work: 512-231-6117
vcard:       cell: 512-569-9461

In response to

pgsql-admin by date

Next:From: Jim NasbyDate: 2006-06-28 00:22:01
Subject: Re: strange fsm issues
Previous:From: Jim NasbyDate: 2006-06-28 00:15:39
Subject: Re: Dump size bigger than pgdata size?

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