From: Tino Schwarze <postgresql@tisc.de>
To: pgsql-admin@postgresql.org
Subject: Re: Where to find information on the new HOT tables?
Date: Wed, 6 Feb 2008 11:20:08 +0100
Message-ID: <20080206102008.GD16997@easy2.in-chemnitz.de> (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>
Hi there,
On Wed, Feb 06, 2008 at 10:11:09AM +0100, Dimitri Fontaine wrote:
> > I'm really not seeing the case for user-level documentation of HOT,
> > when for instance most of the planner's optimization behavior is not
> > so documented.
>
> In my POV, the case for HOT to appear in the documentation as been made by the
> PR and Presskit. They both announce HOT to be a major performance addition in
> 8.3 that users will want to benefit from. Now we have to tell some more to
> the users, I think we want to answer those two basic questions:
> - How do I check that I'm using HOT? (you don't, transparent feature, blah)
> - What's HOT is so good about compared to how PostgreSQL used to work?
>
> My proposal was about answering this without requiring the user to be capable
> of understanding internals and 'developer topics'.
Which might be pretty difficult, if it's an internal feature. But a
short HOT-FAQ would be great, something like this:
- What is HOT?
...
- How do I exploit it?
Make sure that ...
- When will HOT kick in?
If ...
and ...
and ...
> 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.
Yes, I praise it, too! Even though it needs some reading and thinking
and reading and thinking to understand, e.g. the internals of VACUUM or
freeze_max_age etc., the documentation is very helpful to understand
what's going on.
> To ease PostgreSQL newbies manual grasping, I certainly don't think it will
> need shortening the documentation.
Maybe there could be quickstart chapters or HOWTOs.
Bye,
Tino.
--
www.craniosacralzentrum.de
www.spiritualdesign-chemnitz.de
Tino Schwarze * Lortzingstraße 21 * 09119 Chemnitz
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: postgresql@tisc.de
Subject: Re: Where to find information on the new HOT tables?
In-Reply-To: <20080206102008.GD16997@easy2.in-chemnitz.de>
* 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