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

Re: BUG #5082: I can't get logfile( achive )

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: smuffy <vday1945(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5082: I can't get logfile( achive )
Date: 2009-09-28 02:13:07
Message-ID: 603c8f070909271913p3448bbf6l1a57cc8fc6c8e5bd@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Sep 25, 2009 at 11:50 AM, smuffy <vday1945(at)gmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5082
> Logged by:          smuffy
> Email address:      vday1945(at)gmail(dot)com
> PostgreSQL version: 8.4.0
> Operating system:   opensuse 10.2
> Description:        I can't get logfile( achive )
> Details:
>
> hello.
>
> My DB can't make a logfile( archive ).
> But archive_mode is on.(postgresql.conf)
> How I get a logfile?
> help me, please.

This isn't a bug; it's a usage question that should be posted to
pgsql-general or pgsql-novice.

Probably the first thing you want to do is look through your server
logs and see if there are any informative error messages in there, or
any indication of archiving activity.

One possibility is that you aren't generating very much WAL activity,
so it's taking a very long time between archive files.  You could try
issuing an explicit CHECKPOINT or setting archive_timeout.

...Robert

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2009-09-28 02:18:30
Subject: Re: Encounter shared memory error when running createlang command!
Previous:From: JesperDate: 2009-09-27 21:29:39
Subject: BUG #5083: Problem create account.

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