From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Gravsjö <robert(at)blogg(dot)se>, liuzg4 liuzg4 <liuzg4(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: [GENERAL] how to select temp table |
Date: | 2009-05-06 21:19:33 |
Message-ID: | 20090506211933.GO4476@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
Tom Lane escribió:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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.
Yeah, perhaps ... I think it should suggest all index entries that
start with the search string, not necessarily equal.
Magnus? :-)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-05-07 13:44:18 | Re: [GENERAL] how to select temp table |
Previous Message | Tom Lane | 2009-05-06 21:11:38 | Re: [GENERAL] how to select temp table |
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Jones | 2009-05-06 21:30:37 | Re: date ranges in where |
Previous Message | Adrian Klaver | 2009-05-06 21:19:07 | Re: date ranges in where |