Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id E4232632EEC for ; Wed, 21 Jul 2010 22:03:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 03203-07 for ; Thu, 22 Jul 2010 01:03:20 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f174.google.com (mail-gx0-f174.google.com [209.85.161.174]) by mail.postgresql.org (Postfix) with ESMTP id CCDAA632663 for ; Wed, 21 Jul 2010 22:03:21 -0300 (ADT) Received: by gxk23 with SMTP id 23so4060597gxk.19 for ; Wed, 21 Jul 2010 18:03:19 -0700 (PDT) Received: by 10.224.69.16 with SMTP id x16mr788122qai.284.1279760599596; Wed, 21 Jul 2010 18:03:19 -0700 (PDT) Received: from Craig-Jamess-MacBook-Pro.local (wsip-70-167-124-126.sd.sd.cox.net [70.167.124.126]) by mx.google.com with ESMTPS id fb41sm30101389qcb.15.2010.07.21.18.03.18 (version=SSLv3 cipher=RC4-MD5); Wed, 21 Jul 2010 18:03:18 -0700 (PDT) Message-ID: <4C4798D5.7030700@emolecules.com> Date: Wed, 21 Jul 2010 18:03:17 -0700 From: Craig James User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Using more tha one index per table References: <4C46A23B.2090606@acteos.com> <4C470B69.6080304@2ndquadrant.com> <4C47953D.9090603@postnewspapers.com.au> In-Reply-To: <4C47953D.9090603@postnewspapers.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201007/307 X-Sequence-Number: 39696 On 7/21/10 5:47 PM, Craig Ringer wrote: > 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. 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. By using "current" and encouraging people to link to that, we could quickly change the Google pagerank so that a search for Postgres would turn up the most-recent version of documentation. Craig