Re: Small GIN optimizations (after 9.4)
От | Alexander Korotkov |
---|---|
Тема | Re: Small GIN optimizations (after 9.4) |
Дата | |
Msg-id | CAPpHfdsxxqRNVNQpxxeH4anvgx3yC-1M7+97GN7UzzMXnKEv1A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Small GIN optimizations (after 9.4) (Bruce Momjian <bruce@momjian.us>) |
Список | pgsql-hackers |
On Wed, Feb 12, 2014 at 2:58 AM, Bruce Momjian <bruce@momjian.us> wrote:
------
With best regards,
Alexander Korotkov.
On Sun, Feb 9, 2014 at 02:17:12PM +0400, Alexander Korotkov wrote:
> On Thu, Feb 6, 2014 at 8:31 PM, PostgreSQL - Hans-J rgen Sch nig <> postgres@cybertec.at> wrote:Would any of the listed changes cause backward-incompatible changes to
>
> i think there is one more thing which would be really good in GIN and which
> would solve a ton of issues.
> atm GIN entries are sorted by item pointer.
> if we could sort them by a "column" it would fix a couple of real work
> issues such as ...
>
> SELECT ... FROM foo WHERE "tsearch_query" ORDER BY price DESC LIMIT
> 10
>
> ... or so.
> it many cases you want to search for a, say, product and find the cheapest
> / most expensive one.
> if the tsearch_query yields a high number of rows (which it often does) the
> subsequent sort will kill you.
>
>
> This is not intended to be a small change. However, some solution might be
> possible in post 9.4 gin improvements or in new secret indexing project which
> will be presented at PGCon :-)
the on-disk format, causing problems for pg_upgrade?
None of them.
------
With best regards,
Alexander Korotkov.
В списке pgsql-hackers по дате отправления: