public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Added documentation about caching, reliability
Date: Thu, 29 Sep 2005 11:17:00 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Well, now the chapter is about WAL and reliability, so I thought
> > reliability hit both topics. Also, maybe we should consider moving 
> > this FAQ item into the docs:
> >
> >     <H3><A name="3.7">3.7</A>) What computer hardware should I
> > use?</H3>
> 
> Hardware choice and configuration are important topics, but neither of 
> these are strongly tied to either WAL or Reliability.  Reliability is 
> the property (not a "feature") of a system to do what you meant for it 
> to do.  Certainly WAL contributes to that by increasing tolerance 
> against hardware failures, but it still seems to be a rather 
> far-fetched connection to pair these two.
> 
> I could see hardware issues being discussed in chapter 16, since we 
> already have operating system and kernel configuration there, and it's 
> the chapter a user will read when setting up a server system.
> 
> I was never all that happy with the WAL chapter, since, as you say, it 
> doesn't seem to be a first-class user-level feature.  I'd be happy to 
> integrate it into another chapter, but I'm not sure where.

Sure, I am looking for suggestions.  My relabeling at least fixes that,
but feel free to move things around and relabel them.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [email protected]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

view thread (16+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Added documentation about caching, reliability
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox