From: Torsten Zühlsdorff <foo@meisterderspiele.de>
To: pgsql-performance@postgresql.org
Subject: Re: Using more tha one index per table
Date: Fri, 23 Jul 2010 11:22:18 +0200
Message-ID: <i2bn0a$12p$1@news.eternal-september.org> (raw)
In-Reply-To: <4C4798D5.7030700@emolecules.com>
References: <4C46A23B.2090606@acteos.com>
<4C470B69.6080304@2ndquadrant.com>
<4C47953D.9090603@postnewspapers.com.au>
<4C4798D5.7030700@emolecules.com>
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
>
> http://www.postgresql.org/docs/current/static/sql-insert.html
>
> If you google for "postgres insert", you get this:
>
> http://www.postgresql.org/docs/8.1/static/sql-insert.html
>
> 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.
(http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html)
Greetings from Germany,
Torsten
--
http://www.dddbl.de - ein Datenbank-Layer, der die Arbeit mit 8
verschiedenen Datenbanksystemen abstrahiert,
Queries von Applikationen trennt und automatisch die Query-Ergebnisse
auswerten kann.
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: foo@meisterderspiele.de, pgsql-performance@postgresql.org
Subject: Re: Using more tha one index per table
In-Reply-To: <i2bn0a$12p$1@news.eternal-september.org>
* 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