HELP!!! The WAL Archive is taking up all space

Поиск
Список
Период
Сортировка
От FattahRozzaq
Тема HELP!!! The WAL Archive is taking up all space
Дата
Msg-id CAKnA-A1nFT_WuLyqi-cm8po+dAak3VyFEapE43ncehxBQeDMag@mail.gmail.com
обсуждение исходный текст
Ответы Re: HELP!!! The WAL Archive is taking up all space  (Michael Paquier <michael.paquier@gmail.com>)
Re: HELP!!! The WAL Archive is taking up all space  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-hackers
Hi all,

Please help...

I have 1 master PostgreSQL and 1 standby PostgreSQL.
Both servers has the same OS Linux Debian Wheezy, the same hardware.

Both server hardware:
CPU: 24 cores
RAM: 128GB
Disk-1: 800GB SAS (for OS, logs, WAL archive directory)
Disk-2: 330GB SSD (for PostgreSQL data directory, except WAL archive
and except pg_log)

The part of the configuration are as below:
checkpoint_segments = 64
checkpoint_completion_target = 0.9
default_statistics_target = 10
maintenance_work_mem = 1GB
effective_cache_size = 64GB
shared_buffers = 24GB
work_mem = 5MB
wal_buffers = 8MB
wal_keep_segments = 4096
wal_level = hot_standby
max_wal_senders = 10
archive_mode = on
archive_command = 'cp -i %p /home/postgres/archive/master/%f'


The WAL archive is at /home/postgres/archive/master/, right?
This directory consume more than 750GB of Disk-1.
Each segment in the /home/postgres/archive/master/ is 16MB each
There are currently 47443 files in this folder.

I want to limit the total size use by WAL archive to around 200-400 GB.

Do I set the segment too big?
wal_keep_segments = 4096
checkpoint_segments = 64

What value should I set for it?



Regards,
Fattah



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

Предыдущее
От: "Olson, Ken"
Дата:
Сообщение: Re: dynloader.h missing in prebuilt package for Windows?
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: Fwd: Another little thing about psql wrapped expanded output