| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Elias Ghanem <e(dot)ghanem(at)acteos(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Using more tha one index per table |
| Date: | 2010-07-22 00:47:57 |
| Message-ID: | 4C47953D.9090603@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-performance |
On 21/07/10 22:59, Greg Smith wrote:
> A useful trick to know is that if you replace the version number
> with "current", you'll get to the latest version most of the time
> (sometimes the name of the page is changed between versions, too, but
> this isn't that frequent).
The docs pages could perhaps benefit from an auto-generated note saying:
"The current version of Pg is 8.4. This documentation is for version
8.2. Click [here] for documentation on the current version."
... or something to that effect. It'd be a nice (and more user-friendly)
alternative to url twiddling when searches reveal docs for an old
version, and might help push the /current/ pages up in search rank too.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig James | 2010-07-22 01:03:17 | Re: Using more tha one index per table |
| Previous Message | Peter Eisentraut | 2010-07-21 19:32:45 | Re: Please provide stable target anchors |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig James | 2010-07-22 01:03:17 | Re: Using more tha one index per table |
| Previous Message | Pavel Stehule | 2010-07-21 17:21:55 | Re: potential performance gain by query planner optimization |