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
postg...@cybertec.at wrote:
i think there is one more thing which would be really good in GIN and
which
would solve a ton of issues.
atm GIN
On Wed, Feb 12, 2014 at 2:58 AM, Bruce Momjian br...@momjian.us wrote:
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
postg...@cybertec.at wrote:
i think there is one more thing which would be
On Thu, Feb 6, 2014 at 8:31 PM, PostgreSQL - Hans-Jürgen Schönig
postg...@cybertec.at wrote:
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
On Thu, Feb 6, 2014 at 3:36 PM, Heikki Linnakangas
hlinnakan...@vmware.comwrote:
While hacking on the GIN patches, I've come up with a few different ideas
for improving performance. It's too late for 9.4, but I'll list them here
if someone wants to work on them later:
* Represent
While hacking on the GIN patches, I've come up with a few different
ideas for improving performance. It's too late for 9.4, but I'll list
them here if someone wants to work on them later:
* Represent ItemPointers as uint64's, to speed up comparisons.
ginCompareItemPointers is inlined into
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
