pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frederiko Costa <frederiko@gmail.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: archived WALL files question
Date: Mon, 19 Apr 2010 10:49:51 -0700
Message-ID: <4BCC97BF.8090501@gmail.com> (raw)
In-Reply-To: <4BCC4BEB0200002500030A75@gw.wicourts.gov>
References: <7965A9DCF12CC14984420BCC37B1608F25AC0B99AD@Elzar.grant.co.uk>
	<4BC6F21D0200002500030956@gw.wicourts.gov>
	<7965A9DCF12CC14984420BCC37B1608F25AC0B99E4@Elzar.grant.co.uk>
	<4BCC7804.9070604@gmail.com>
	<4BCC415D0200002500030A6B@gw.wicourts.gov>
	<4BCC8E76.2040105@gmail.com>
	<4BCC4BEB0200002500030A75@gw.wicourts.gov>



On 04/19/2010 10:26 AM, Kevin Grittner wrote:
> Frederiko Costa<frederiko@gmail.com>  wrote:
>    
>> I have seen new 16 MB segments files created in pg_xlog directory
>> as time goes on. Honestly, I did not understand why it got
>> created, because I was running it on a VM and there was no
>> activity. I got several new segments.
>>
>> If I run the command you asked, this is the output. Neither
>> segment is copied, nor a new segment file gets created:
>>
>>    select pg_switch_xlog();
>>    pg_switch_xlog
>> ----------------
>>    0/81000088
>> (1 row)
>>      
>
> What version of PostgreSQL is this?
>    
8.4.3
>
> What do you see if you run?:
>
> show archive_command;
>    
cp -p %p /mnt/data/%f
> show archive_mode;
>    
on
> show archive_timeout;
>    
1min
I have just enabled that. Now, log files are being copied directly to 
the /mnt/data dir. However, the same segments are not in the pg_xlog 
dir. Is this a default behaviour?

Must I set archive_timeout? I don't think I want that, because, 
specially for the next few months, where the activity would be very 
limited and I would get several zero written segments just because 
timeout has been reached. Is this approach recommended anyway? Or is it 
better to use this approach even having limited approach?

> Check your log file from the time you ran pg_switch_xlog to look for
> any messages which might give a clue to what's happening.
>
>    
The log files did not write anything about pg_switch_xlog.
> -Kevin
>    



view thread (15+ messages)  latest in thread

Message-ID: <4BCC97BF.8090501@gmail.com>
Permalink:  ../4BCC97BF.8090501@gmail.com/
Also on:    postgresql.org/message-id/4BCC97BF.8090501@gmail.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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: frederiko@gmail.com, Kevin.Grittner@wicourts.gov
  Subject: Re: archived WALL files question
  In-Reply-To: <4BCC97BF.8090501@gmail.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