On Thu, Jul 05, 2007 at 12:26:45PM +0100, Heikki Linnakangas wrote:
Kenneth Marshall wrote:
I definitely agree with Tom's assessment. If we cannot need to make the
hash index as performant as it is in theory, none of the other refinements
are worth it. You would need to use BTree if you were
Kenneth Marshall wrote:
I definitely agree with Tom's assessment. If we cannot need to make the
hash index as performant as it is in theory, none of the other refinements
are worth it. You would need to use BTree if you were concerned about
speed. (and who isn't)
I just got an idea.
Hash
Wow... not sure how I missed that. I *did* create this schema ages ago,
perhaps it wasn't there, or at the time I had no idea what the
implications were. *shrug*
Regards,
- Naz.
Tom Lane wrote:
Naz Gassiep [EMAIL PROTECTED] writes:
As a result, when creating tables containing
Ühel kenal päeval, E, 2007-07-02 kell 04:27, kirjutas Naz Gassiep:
I've been warned away from hash indexes before, however I had no idea
that it's performance was that abysmal that BTREE beat it and I was
definitely not aware that they were not included in WAL logs. I was told
it wasn't as
Actually I think the *most* important thing to work on is to get hash to
the point where its search speed actually beats btree consistently, so
that it has an excuse to live. If that is insoluble we might well end up
ripping it out entirely. (The first three TODO items for hash indexes
are
Naz Gassiep [EMAIL PROTECTED] writes:
As a result, when creating tables containing large blocks of text I wish
to index, I've been using HASH as an index method. Please can we state
in the manual that HASH index types are in a beta stage of development
or something similar, or perhaps remove
[EMAIL PROTECTED] wrote:
Is anyone currently working on this TODO item?
During index creation, pre-sort the tuples to improve build speed
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01199.php
A few of us would like to tackle it and see if we can add some value here.
That
Heikki Linnakangas [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
Is anyone currently working on this TODO item?
During index creation, pre-sort the tuples to improve build speed
If you want to work on hash indexes, though, this TODO item seems more
important to me at least:
Add WAL
On Wed, Jun 27, 2007 at 08:36:54PM -0400, Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
Is anyone currently working on this TODO item?
During index creation, pre-sort the tuples to improve build speed
If you want to work on hash indexes, though,
