Re: 2,2gb of pg_xlog ??

Поиск
Список
Период
Сортировка
От Andy Shellam
Тема Re: 2,2gb of pg_xlog ??
Дата
Msg-id !~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAAC4AAAAAAAAAt+qV6pqKPEmXG74TlFgX5gEAlpDSN+DrMEWnumhoRHpQKQAAAbLc9wAAEAAAAKU80G+9fHJEvpPLmsTf0SEBAAAAAA==@andycc.net
обсуждение исходный текст
Ответ на Re: 2,2gb of pg_xlog ??  ("Chris Hoover" <revoohc@gmail.com>)
Список pgsql-admin

I agree about the upgrade, surely there was a way of archiving the transaction logs in 7.2, otherwise with very large databases you could have transaction logs backing up over tens of GBs, and no way to rid of them!

 

 


From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Chris Hoover
Sent: 22 June 2006 3:12 pm
To: andy.shellam@mailnetwork.co.uk
Cc: Stefan.Schmidt@schinkel.de; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] 2,2gb of pg_xlog ??

 

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,449aa5c7256843821515230!

В списке pgsql-admin по дате отправления:

Предыдущее
От: "Andy Shellam"
Дата:
Сообщение: Re: 2,2gb of pg_xlog ??
Следующее
От: Tom Lane
Дата:
Сообщение: Re: 2,2gb of pg_xlog ??