From: Chris Hoover <revoohc@gmail.com>
To: andy.shellam@mailnetwork.co.uk
Cc: Stefan.Schmidt@schinkel.de
Cc: pgsql-admin@postgresql.org
Subject: Re: 2,2gb of pg_xlog ??
Date: Thu, 22 Jun 2006 10:12:04 -0400
Message-ID: <1d219a6f0606220712k3be5d72fra35a3af8d10ea072@mail.gmail.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAAC4AAAAAAAAAt+qV6pqKPEmXG74TlFgX5gEAlpDSN+DrMEWnumhoRHpQKQAAAbLc9wAAEAAAANc7qPyPxh1JrLXPElQequQBAAAAAA==@andycc.net>
References: <0000EA81.4497EA95@192.168.3.13>
<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAAC4AAAAAAAAAt+qV6pqKPEmXG74TlFgX5gEAlpDSN+DrMEWnumhoRHpQKQAAAbLc9wAAEAAAANc7qPyPxh1JrLXPElQequQBAAAAAA==@andycc.net>
None of this will work since he is using PG 7.2. To start off with, and
urgent upgrade is needed to a newer version since there are serious bugs and
data loss issues in these earlier versions.
As far as having the 2.2 GB of xlogs, someone more knowledgeable of this
would need to answer that.
On 6/22/06, Andy Shellam <andy@andycc.net> wrote:
>
> Hi Stefan,
>
>
>
> These pg_xlog files are, as you said, 16MB files that store all the
> transactions made to your database – if you're doing regular SQL dump
> backups, and you know you won't need Point-In-Time (PITR) recovery, you
> won't need these files.
>
>
>
> However, you will need to arrange for old files to be automatically
> archived into a separate folder outside of your pg_xlog directory, by
> setting an archive_command in the WAL configuration in postgresql.conf. A
> dead simple command looks like this:
>
>
>
> Archive_command = "mv %p /your/backup/directory/%f"
>
>
>
> This tells PGSQL to move ("mv") the file no longer in use "%p" to the
> directory "/your/backup/directory/" with the filename "%f". %f is the
> original filename of the file being archived.
>
>
>
> Once you've put that in, killall –HUP postmaster, and you should notice
> your files being moved out. Note: the postgresql Unix user (from
> /etc/passwd) will need write access to /your/backup/directory.
>
>
>
> Tip: if you're absolutely sure you will never need these transaction logs,
> you can use the following command to delete them when they're finished with:
>
>
>
> Archive_command = "rm –f %p"
>
>
>
> Or
>
>
>
> Archive_command = "mv %p /dev/null"
>
>
>
> This is for PostgreSQL 8.0 above, I believe it should be the same for 7.2.
>
>
>
> Hope this helps!
>
>
>
> Andy
>
>
>
>
> ------------------------------
>
> *From:* pgsql-admin-owner@postgresql.org [mailto:
> pgsql-admin-owner@postgresql.org] *On Behalf Of *
> Stefan.Schmidt@schinkel.de
> *Sent:* 20 June 2006 11:31 am
> *To:* pgsql-admin@postgresql.org
> *Subject:* [ADMIN] 2,2gb of pg_xlog ??
>
>
>
> Hi,
>
>
>
> I'm new to pgsql, so please be kind ;-)
>
>
>
> ok here my problem:
>
>
>
> I have a linux box with Debian Woody and pgsql 7.2.
>
>
>
> The problem is in the pg_xlog hold about 137 files with 16 MB each, the
> oldest file is from 2005.
>
>
>
> I read the WAL docu but as far as I'm understandig it, it should be auto
> cleand as long as isn't configured otherwise.
>
> But it is not, all options mentioned in the WAL doku are not set..
>
>
>
> Any suggestions?
>
>
>
> here is my postgres.conf
>
>
>
> ------
>
>
> fsync = off
>
> debug_level = 0
> log_connections = off
> log_pid = on
> log_timestamp = on
> syslog = 1
> # if syslog is 0, turn silent_mode off!
> silent_mode = off
> syslog_facility = LOCAL0
> trace_notify = off
> max_connections = 64
> # shared_buffers must be at least twice max_connections, and not less than
> 16
> shared_buffers = 128
> # TCP/IP access is allowed by default, but the default access given in
> # pg_hba.conf will permit it only from localhost, not other machines.
> tcpip_socket = on
> sort_mem = 512
>
>
>
>
> ------
>
>
>
> cu
>
>
>
> !DSPAM:14,449a31b6256849416340232!
>
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: revoohc@gmail.com, andy.shellam@mailnetwork.co.uk, Stefan.Schmidt@schinkel.de
Subject: Re: 2,2gb of pg_xlog ??
In-Reply-To: <1d219a6f0606220712k3be5d72fra35a3af8d10ea072@mail.gmail.com>
References: <0000EA81.4497EA95@192.168.3.13> <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAAC4AAAAAAAAAt+qV6pqKPEmXG74TlFgX5gEAlpDSN+DrMEWnumhoRHpQKQAAAbLc9wAAEAAAANc7qPyPxh1JrLXPElQequQBAAAAAA==@andycc.net> <1d219a6f0606220712k3be5d72fra35a3af8d10ea072@mail.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