| From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
|---|---|
| To: | jesper(at)krogh(dot)cc |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: wal-size limited to 16MB - Performance issue for subsequent backup |
| Date: | 2014-10-20 19:27:21 |
| Message-ID: | 20141020192721.GF32559@aart.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 20, 2014 at 09:03:59PM +0200, jesper(at)krogh(dot)cc wrote:
> Hi.
>
> One of our "production issues" is that the system generates lots of
> wal-files, lots is like 151952 files over the last 24h, which is about
> 2.4TB worth of WAL files. I wouldn't say that isn't an issue by itself,
> but the system does indeed work fine. We do subsequently gzip the files to
> limit actual disk-usage, this makes the files roughly 30-50% in size.
>
> ...
>
> Suggestions are welcome. An archive-command/restore command that could
> combine/split wal-segments might be the easiest workaround, but how about
> crash-safeness?
>
Hi,
Have you considered using something like tar/star in the archive command
to pack them into much larger tar archives?
Regards,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jesper | 2014-10-20 19:27:39 | Re: wal-size limited to 16MB - Performance issue for subsequent backup |
| Previous Message | Tom Lane | 2014-10-20 19:10:50 | Re: Superuser connect during smart shutdown |