| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PITR backup - estimating size |
| Date: | 2012-03-23 14:52:46 |
| Message-ID: | CAFcNs+qO+DACy8JOwfPwShNrrXLT_tw8-3OqJfUw55OJ3roHtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2012/3/23 Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com>
> I'd like to switch to PITR backups, but have limited disk space. Is there
> a way to get a ballpark estimate by monitoring a running system, without
> actually creating the WAL files and risking filling a filesystem?
>
>
> Usually each wal segment size is 16MB (16777216 bytes), so you can save
this information using "archive_command". Ex:
archive_command = 'du -b %p >> /tmp/xlogsize_history.txt'
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2012-03-23 14:53:03 | Re: PostgreSQL 64 Bit XIDs - Transaction IDs |
| Previous Message | Mike Blackwell | 2012-03-23 14:34:07 | PITR backup - estimating size |