From: =?ISO-8859-1?Q?Torsten_Z=FChlsdorff?= <foo@meisterderspiele.de>
Subject: Re: Using more tha one index per table
Date: Fri, 23 Jul 2010 11:22:18 +0200
Organization: A noiseless patient Spider
Lines: 40
Message-ID: <i2bn0a$12p$1@news.eternal-september.org>
References: <4C46A23B.2090606@acteos.com> <4C470B69.6080304@2ndquadrant.com>
	<4C47953D.9090603@postnewspapers.com.au>
	<4C4798D5.7030700@emolecules.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 23 Jul 2010 09:22:18 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
	posting-host="AnkPUomeHXvuN7UdHvIkog";
	logging-data="1113"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+KKXHWx2pWo7gsP9k7xbd4"
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de;
	rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0
In-Reply-To: <4C4798D5.7030700@emolecules.com>
Cancel-Lock: sha1:HmfuLNIATqcrAwco3MDhim6uaAk=
To: pgsql-performance@postgresql.org

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.