From: "Dave Page" <dpage@vale-housing.co.uk>
To: <jd@commandprompt.com>
Cc: <pgsql-www@postgresql.org>
Subject: Re: Search thoughts
Message-ID: <000f01c67526$2c662ab3$6a01a8c0@valehousing.co.uk>
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 11 May 2006 19:10:24 +0100
MIME-Version: 1.0
thread-topic: [pgsql-www] Search thoughts
thread-index: AcZ1Go0hQqpa+O/QRuiD7LY544/e2gAC59HU


-----Original Message-----
From: "Joshua D. Drake"<jd@commandprompt.com>
Sent: 11/05/06 17:47:12
To: "Joshua D. Drake"<jd@commandprompt.com>
Cc: "PostgreSQL WWW"<pgsql-www@postgresql.org>
Subject: Re: [pgsql-www] Search thoughts

> Reposting because I realize that everyone was in bed or heading home=20
> when this came through:

Huh? Your email vanishes if you aren't there to read it as soon as it =
arrives? :-)

And, no, I don't mind if you wanna tweak the weights.

/D

-----Unmodified Original Message-----
Reposting because I realize that everyone was in bed or heading home=20
when this came through:

Joshua D. Drake wrote:
> Hello,
>=20
> I have been doing some example searching with our search engine and =
was=20
> wondering if we can adjust the weights a little differently. For =
example:
>=20
> ALTER TABLE, first link is:
>=20
> =
http://www.postgresql.org/files/documentation/books/aw_pgsql/node203.html=

>=20
> Which although accurate is way out dated. It seems we should weight a=20
> docs search higher with the current docs having the most weight?
>=20
> The same happens with many of the commands such as CREATE INDEX...
>=20
> Joshua D. Drake
>=20


--=20

            =3D=3D=3D The PostgreSQL Company: Command Prompt, Inc. =
=3D=3D=3D
      Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
      Providing the most comprehensive  PostgreSQL solutions since 1997
                     http://www.commandprompt.com/


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@postgresql.org so that your
       message can get through to the mailing list cleanly