pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Maximum Possible Insert Performance?
Date: Tue, 25 Nov 2003 11:36:50 +0530
Message-ID: <3FC2F17A.5050307@persistent.co.in> (raw)
In-Reply-To: <bpteip$13d$1@news.hub.org>
References: <bprv1q$1j5o$1@news.hub.org>
	<3FC19C2C.4050704@myrealbox.com>
	<bpteip$13d$1@news.hub.org>

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? 
> There's quite a few 512MB/1GB/2GB solid state drives available now in 
> the ~$200-$500 range and if you never hit those limits...

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.

Correct me if I am wrong..

  Shridhar




view thread (19+ messages)  latest in thread

Message-ID: <3FC2F17A.5050307@persistent.co.in>
Permalink:  ../3FC2F17A.5050307@persistent.co.in/
Also on:    postgresql.org/message-id/3FC2F17A.5050307@persistent.co.in

 · 

reply

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: shridhar_daithankar@persistent.co.in, wyu@talisys.com
  Subject: Re: Maximum Possible Insert Performance?
  In-Reply-To: <3FC2F17A.5050307@persistent.co.in>

* 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