From: Tom Lane <tgl@sss.pgh.pa.us>
To: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
Cc: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Maximum Possible Insert Performance?
Date: Tue, 25 Nov 2003 10:47:37 -0500
Message-ID: <27727.1069775257@sss.pgh.pa.us> (raw)
In-Reply-To: <3FC2F17A.5050307@persistent.co.in>
References: <bprv1q$1j5o$1@news.hub.org>
<3FC19C2C.4050704@myrealbox.com>
<bpteip$13d$1@news.hub.org>
<3FC2F17A.5050307@persistent.co.in>
Shridhar Daithankar <shridhar_daithankar@persistent.co.in> writes:
> William Yu wrote:
>> This is an intriguing thought which leads me to think about a similar
>> solution for even a production server and that's a solid state drive for
>> just the WAL. What's the max disk space the WAL would ever take up?
> Maximum number of WAL segments at any time in 2*(number of checkpoint
> segments)+1 IIRC.
> So if you have 3 checkpoint segments, you can not have more than 7 WAL
> segments at any time. Give or take 1.
I don't believe that's a *hard* limit. The system tries to schedule
checkpoints often enough to prevent WAL from getting bigger than that,
but if you had a sufficiently big spike in update activity, it's at
least theoretically possible that more than checkpoint_segments segments
could be filled before the concurrently running checkpoint finishes and
releases some old segments.
The odds of this being a real problem are small, especially if you don't
try to fit on an undersized SSD by reducing checkpoint_segments. I'd
think that a 512Mb SSD would be plenty of space for ordinary update load
levels ...
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, shridhar_daithankar@persistent.co.in, wyu@talisys.com
Subject: Re: Maximum Possible Insert Performance?
In-Reply-To: <27727.1069775257@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