| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GIN fast insert |
| Date: | 2009-02-13 14:02:54 |
| Message-ID: | 603c8f070902130602o7cbceaaew4d7cf4d4604ba80d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 13, 2009 at 8:00 AM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
>> SELECT * FROM foo WHERE t @@ query LIMIT 100
>> might be a fairly common use case.
>
> It seems to me -
> SELECT * FROM foo WHERE t @@ query *ORDER BY rank* LIMIT 100;
I'm not sure you can really assume that the ORDER BY rank will always
be in there.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Marshall | 2009-02-13 14:04:58 | Re: [PERFORM] GIST versus GIN indexes for intarrays |
| Previous Message | Teodor Sigaev | 2009-02-13 13:12:53 | Re: [PERFORM] GIST versus GIN indexes for intarrays |