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 10:40:51 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Peter Eisentraut wrote:
> Am Mittwoch, 28. September 2005 20:26 schrieb Bruce Momjian:
> > I also renamed the chapter "Reilability" rather than "WAL."
> 
> Considering that the chapter is, in fact, all about WAL, I don't think this is 
> a good move.  Reliability is a concern that is not only addressed by the WAL 
> system.  Please change it back.

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>

    <P>Because PC hardware is mostly compatible, people tend to believe that
    all PC hardware is of equal quality.  It is not.  ECC RAM, SCSI, and
    quality motherboards are more reliable and have better performance than
    less expensive hardware.  PostgreSQL will run on almost any hardware,
    but if reliability and performance are important it is wise to
    research your hardware options thoroughly.  Our email lists can be used
    to discuss hardware options and tradeoffs.</P>

Anyway, I thought the previous chapter title, WAL, was weird because it
was hard to know why an administrator would care about WAL --- there was
no lead-in to the term.  This way, it is all under reliability, and can
add to it.

-- 
  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