Re: Using more tha one index per table

From: Torsten Zühlsdorff <foo(at)meisterderspiele(dot)de>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Using more tha one index per table
Date: 2010-07-23 09:22:18
Message-ID: i2bn0a$12p$
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-docs pgsql-performance

Craig James schrieb:

>>> 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.
> In addition, why not use symlinks so that the current version is simply
> called "current", as in
> If you google for "postgres insert", you get this:
> The problem is that Google ranks pages based on inbound links, so older
> versions of Postgres *always* come up before the latest version in page
> ranking.

Since 2009 you can deal with this by defining the canonical-version.

Greetings from Germany,

-- - ein Datenbank-Layer, der die Arbeit mit 8
verschiedenen Datenbanksystemen abstrahiert,
Queries von Applikationen trennt und automatisch die Query-Ergebnisse
auswerten kann.

In response to


Browse pgsql-docs by date

  From Date Subject
Next Message John Gage 2010-07-23 10:02:02 Adding a crucial element to an example
Previous Message Thom Brown 2010-07-22 22:02:21 Tidy up boolean data type page

Browse pgsql-performance by date

  From Date Subject
Next Message Joshua Tolley 2010-07-23 15:55:35 Re: Pooling in Core WAS: Need help in performance tuning.
Previous Message Pavel Stehule 2010-07-23 07:43:27 Re: Execution Plan