From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Svenne Krap <svenne(at)krap(dot)dk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: LIMIT NULL |
Date: | 2009-02-04 17:22:23 |
Message-ID: | A73078CF-B266-42F0-91CA-1831C73205F4@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 4, 2009, at 5:25 AM, Andrew Dunstan wrote:
> In effect it does say that - perhaps not quite as explicitly as you
> might have wanted. It says: "The information in this part is
> presented in a narrative fashion in topical units. Readers looking
> for a complete description of a particular command should look into
> Part VI. " (the "PART VI" is a link).
Which would make sense if you were reading it as a book, from front to
back. But as Svenn, Rick, and I have shown, that's not how people find
PostgreSQL documentation. There should be cross references to the
proper pages in Part VI on every relevant page in the narrative
sections, IMHO.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2009-02-04 17:22:35 | Re: Review: B-Tree emulation for GIN |
Previous Message | Kevin Grittner | 2009-02-04 17:15:14 | Re: add_path optimization |