| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: No control over max.num. WAL files |
| Date: | 2011-05-25 12:55:14 |
| Message-ID: | 4DDCFC32.4080704@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> These are the relevant parameters we have changed in postgresql.conf:
>
> archive_mode | off
> checkpoint_segments | 128
> default_statistics_target | 100
> maintenance_work_mem | 512MB
> max_fsm_pages | 800000
> max_fsm_relations | 8000
> shared_buffers | 10GB
> wal_buffers | 512kB
> wal_sync_method | fdatasync
> work_mem | 16MB
Are you sure you don't also have WAL archiving enabled? That can easily
lead to too many WAL segments being kept if the archiving process can't
keep up or fails.
It'd really help if you could show part of your postgresql logs from the
during restore.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafael Martinez | 2011-05-25 13:13:38 | Re: No control over max.num. WAL files |
| Previous Message | Scott Marlowe | 2011-05-25 12:53:00 | Re: No control over max.num. WAL files |