Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 3CE56632663 for ; Wed, 21 Jul 2010 22:47:57 -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 24487-05 for ; Thu, 22 Jul 2010 01:47:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id 10B1563103A for ; Wed, 21 Jul 2010 22:47:50 -0300 (ADT) Received: from [192.168.1.5] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0LiZ4a-1PBveZ0aWy-00d3cm; Thu, 22 Jul 2010 03:47:47 +0200 Message-ID: <4C47A341.7010905@2ndquadrant.com> Date: Wed, 21 Jul 2010 21:47:45 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Craig James CC: 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> <4C4798D5.7030700@emolecules.com> In-Reply-To: <4C4798D5.7030700@emolecules.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:0TrHbLiyRnZH2LGWrOxPOi6fjJOXCEKdfRv2EqWh6LA o+kmT4RWrRWklh8tywXFxc65S7hJB3AbgSIBKzy5cj+wi1NaQj CHrb5nMOCIEqerIuJM9lRxKDEWv7wFod8o3EhDMO2t+4E+koOl tvDkoWCM3do3ED7Mihqd+PIqqbznNADQYGPjcRxzKFtyUyDZRI pAmwS0cmQvjdBx2ttFzWpiPdlEwYWhH9ovVTPEYPiA= 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, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201007/308 X-Sequence-Number: 39697 Craig James wrote: > 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. How do you propose to encourage people to do that? If I had a good answer to that question, I'd already be executing on it. I've made a habit of doing that when writing articles on the wiki, which hopefully themselves become popular and then elevate those links (all of the ones http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server for example point to current). I don't know how to target "people who link to the PostgreSQL manual" beyond raising awareness of the issue periodically on these lists, like I did on this thread. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us