From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achakzai, Omar <omar.achakzai@logicacmg.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_xlog and the WAL files
Date: Fri, 16 Feb 2007 10:26:26 -0500
Message-ID: <27605.1171639586@sss.pgh.pa.us> (raw)
In-Reply-To: <FCE7AD9975BC4B4E89E2F4EF6049F69201148FBF@nl-ex020.groupinfra.com>
References: <FCE7AD9975BC4B4E89E2F4EF6049F69201148FBF@nl-ex020.groupinfra.com>
"Achakzai, Omar" <omar.achakzai@logicacmg.com> writes:
> 1. What happens when the file system on which the pg_xlog directly resides,=
> completely fills up? Does PostgreSQL wait until free space is available ag=
> ain?=20
I believe it'll PANIC and shut down. You won't lose any committed
transactions ... but transactions in progress are out of luck.
> 2. Our PostgreSQL database (version 8.1.4.) generates almost 20 GB of WAL f=
> iles per hour! What are the best practices related to administering large a=
> mounts of WAL files? Would it be wise to compress the WAL files?=20
What are your checkpoint settings? Reducing checkpoint frequency is one
way to cut the WAL volume.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, omar.achakzai@logicacmg.com
Subject: Re: pg_xlog and the WAL files
In-Reply-To: <27605.1171639586@sss.pgh.pa.us>
References: <FCE7AD9975BC4B4E89E2F4EF6049F69201148FBF@nl-ex020.groupinfra.com> <27605.1171639586@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox