Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: Using more tha one index per table
From: Steve Atkins <steve@blighty.com>
In-Reply-To: <4C47A341.7010905@2ndquadrant.com>
Date: Wed, 21 Jul 2010 19:00:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <91A47C2E-2802-4719-BCC6-B82A125DCB70@blighty.com>
References: <4C46A23B.2090606@acteos.com> <4C470B69.6080304@2ndquadrant.com>
	<4C47953D.9090603@postnewspapers.com.au>
	<4C4798D5.7030700@emolecules.com>
	<4C47A341.7010905@2ndquadrant.com>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>


On Jul 21, 2010, at 6:47 PM, Greg Smith wrote:

> 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.
>=20
> 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. =20

When people link to a page, they link to the URL they copy and paste out =
of the browser address bar.

If http://postgresql.org/docs/9.0/* were to 302 redirect to =
http://postgresql.org/docs/current/* while 9.0 is the current release =
(and similarly for 9.1 and so on) I suspect we'd find many more links to =
current and fewer links to specific versions after a year or two.

> 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.

Cheers,
  Steve