pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adam Tauno Williams <adamtaunowilliams@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Where to find information on the new HOT tables?
Date: Wed, 06 Feb 2008 08:43:32 -0500
Message-ID: <1202305412.5753.13.camel@WM_ADAM1.morrison.iserv.net> (raw)
In-Reply-To: <200802061011.11929.dfontaine@hi-media.com>
References: <1d219a6f0802051142k882827cyd38ea7a3d7c1e4ea@mail.gmail.com>
	<36e682920802052145lc3b566cr1facc1cd76847a5a@mail.gmail.com>
	<2827.1202278590@sss.pgh.pa.us>
	<200802061011.11929.dfontaine@hi-media.com>

> I'd also like to add that people judging documentation effectiveness by its 
> length are certainly not real users of it. I've yet to meet a PostgreSQL user 
> who doesn't praise the product documentation, even if newcomers often need 
> some time to be able to understand where to find what. The Tsearch enabled 
> website has been a huge improvement here.
> To ease PostgreSQL newbies manual grasping, I certainly don't think it will 
> need shortening the documentation.

Agree, 125%.  There are quick start guides for newbies, and a
quadrillion goofy little howtos (although I've come to have some
contempt for the whole "howto" category).   I chose PostgreSQL over
that-other-database because it had useful documentation and smelled like
a "real" database.  I'm also an Informix/DB2 DBA and I think the
documentation is very good,  there can't be too much documentation so
anyone judging on length just needs to be dope-slapped.  [And I've
personally used the TOAST section to tune a database that uses lots of
large values].  The current manual is divided into sections, including a
tutorial so I just don't see any grounds for a complexity complaint at
all.  A new user should, of course, wade into the "System
Administration" section with some sense of trepidation.  

My experience [now extensive] with users of that-other-database is that
they will *ALWAYS* claim *ANYTHING* else is too complicated [most of
them have never used anything else] before starting to explain why they
have two storage backends and the merits between MyISAM and InnoDb;
Sheeesh!

It is important to distinguish between informed criticism and the
triumvirate of laziness, fanboy FUD, and outright whining.

OTOH,  I think a paragraph explaining how HOT causes performance to
differ from previous versions would be sufficient.  It isn't really a
user, or even an admin, tunable AFAIK.  It is just an inherent good in
the current version - but since it was mentioned allot in release
announcements it merits some mention in the docs.
 
Adam Tauno Williams, Network & Systems Administrator
Consultant - http://www.whitemiceconsulting.com
Developer - http://www.opengroupware.org




view thread (34+ messages)  latest in thread

Message-ID: <1202305412.5753.13.camel@WM_ADAM1.morrison.iserv.net>
Permalink:  ../1202305412.5753.13.camel@WM_ADAM1.morrison.iserv.net/
Also on:    postgresql.org/message-id/1202305412.5753.13.camel@WM_ADAM1.morrison.iserv.net

 · 

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-admin@postgresql.org
  Cc: adamtaunowilliams@gmail.com
  Subject: Re: Where to find information on the new HOT tables?
  In-Reply-To: <1202305412.5753.13.camel@WM_ADAM1.morrison.iserv.net>

* 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