From: Tom Lane <tgl@sss.pgh.pa.us>
To: nolan@celery.tssi.com
Cc: gearond@cvc.net
Cc: scrappy@postgresql.org
Cc: cobalt@bearfruit.org
Cc: pgsql-advocacy@postgresql.org
Subject: Re: [GENERAL] interesting PHP/MySQL thread
Date: Tue, 24 Jun 2003 09:59:06 -0400
Message-ID: <18992.1056463146@sss.pgh.pa.us> (raw)
In-Reply-To: <20030624050732.2523.qmail@celery.tssi.com>
References: <20030624050732.2523.qmail@celery.tssi.com>
nolan@celery.tssi.com writes:
> And while i'm on the subject, the only book (hard copy) I've got on
> PostgreSQL is the O'Reilly 'Practical PostgreSQL' book, now a bit dated,
> which has one of the worst indexes I've seen in a computer manual in years.
> It may be the worst index I've ever experienced in an O'Reilly book.
> I've had a series of paper clips, bulldog clips and post-it notes marking
> the sections I tend to reuse frequently, because the index doesn't get
> you there. Most of the time I use the online manual, and I've got a
> few pages that aren't obvious from the table of contents bookmarked for
> the online manual, too.
The online manuals have an index. Could you write up a list of proposed
index additions for us? A few quick <indexentry> commands would be easy
enough to add to the doc sources --- the hard part is knowing what to
index.
regards, tom lane
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, nolan@celery.tssi.com, gearond@cvc.net, scrappy@postgresql.org, cobalt@bearfruit.org, pgsql-advocacy@postgresql.org
Subject: Re: [GENERAL] interesting PHP/MySQL thread
In-Reply-To: <18992.1056463146@sss.pgh.pa.us>
* 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