Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 5B23063247E
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed,  6 May 2009 18:11:51 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 41832-10 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed,  6 May 2009 18:11:48 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 1FDEF62DBDE
	for <pgsql-docs@postgresql.org>; Wed,  6 May 2009 18:11:47 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n46LBduE027901;
	Wed, 6 May 2009 17:11:39 -0400 (EDT)
To: Alvaro Herrera <alvherre@commandprompt.com>
cc: Robert =?iso-8859-1?Q?Gravsj=F6?= <robert@blogg.se>,
	liuzg4 liuzg4 <liuzg4@gmail.com>, pgsql-docs@postgresql.org
Subject: Re: [GENERAL] how to select temp table 
In-reply-to: <20090506205307.GM4476@alvh.no-ip.org> 
References: <f97af4400905060534y6312540aqf9ad2c09b0905472@mail.gmail.com>
	<4A01CFE8.9010005@blogg.se> <20090506192354.GK4476@alvh.no-ip.org>
	<20090506192728.GL4476@alvh.no-ip.org>
	<27338.1241642808@sss.pgh.pa.us>
	<20090506205307.GM4476@alvh.no-ip.org>
Comments: In-reply-to Alvaro Herrera <alvherre@commandprompt.com>
	message dated "Wed, 06 May 2009 16:53:07 -0400"
Date: Wed, 06 May 2009 17:11:38 -0400
Message-ID: <27900.1241644298@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200905/6
X-Sequence-Number: 5167

Alvaro Herrera <alvherre@commandprompt.com> writes:
> Hmm, we have another problem then, which is that GUC vars are not
> showing in the search results when you search for their names.  For
> example if I search for search_path I am suggested 
> http://www.postgresql.org/docs/current/static/ddl-schemas.html#DDL-SCHEMAS-PATH
> but nothing else.

> Oh, I see the problem .. the index entry is "search_path configuration
> parameter".  I think it would be better if it were

> <primary>search_path</><secondary>configuration parameter</>

Seems like what you are describing is a bug in the search engine,
not a problem we must address by doubling the vertical space needed for
literally hundreds of index entries.

			regards, tom lane