From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
---|---|
To: | "Joshua b(dot) Jore" <josh(at)greentechnologist(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Insight into indexes? (or inverting then externally) |
Date: | 2002-06-05 19:31:01 |
Message-ID: | 20020605153101.6ad18d58.nconway@klamath.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 5 Jun 2002 09:07:37 -0500 (CDT)
"Joshua b. Jore" <josh(at)greentechnologist(dot)org> wrote:
> So before I jump down this rabbit hole is there anything I can do to
> PostgreSQL to see what is in the indexes and if there is any way to tweak
> them?
Exactly what would you like to "tweak"? I'm not really sure what the
problem is...
> And when is a hash index preferrable to a btree index?
Never (if you know of a situation in which hash has a significant
advantage over btree, let me know -- I haven't been able to find one).
The current hash index code doesn't handle multiple columns, unique
indexes, tends to deadlock under heavy concurrent access, and is VERY
slow to create.
> Or that other index type that I don't remember the name of.
You're probably thinking of rtree, which is for non-scalar data (and
thus, isn't an option for you AFAICT).
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | sheetal | 2002-06-05 20:06:36 | Help... |
Previous Message | Jason Earl | 2002-06-05 18:49:39 | Re: EASY!!! Timestamp conversion & php |