btree gist known problems
I'm looking for known problem areas in btree_gist. I see:
http://archives.postgresql.org/message-id/8973.1286841006@sss.pgh.pa.us
With Range Types, I'm anticipating that btree_gist will become more
important, so I'd like to know what bugs are holding it back.
So, anything else come to mind? Or does btree_gist just need a good
review? Or have the problems been fixed?
Regards,
Jeff Davis
Jeff Davis <pgsql@j-davis.com> writes:
I'm looking for known problem areas in btree_gist. I see:
http://archives.postgresql.org/message-id/8973.1286841006@sss.pgh.pa.us
With Range Types, I'm anticipating that btree_gist will become more
important, so I'd like to know what bugs are holding it back.
So, anything else come to mind? Or does btree_gist just need a good
review? Or have the problems been fixed?
The thing I was complaining about in the referenced message is specific
to the inet opclass; it's unfair to make it sound like it's a generic
problem with btree_gist. And no, it's not been fixed AFAIK.
regards, tom lane
On Mon, 2011-11-07 at 10:18 -0500, Tom Lane wrote:
Jeff Davis <pgsql@j-davis.com> writes:
I'm looking for known problem areas in btree_gist. I see:
http://archives.postgresql.org/message-id/8973.1286841006@sss.pgh.pa.usWith Range Types, I'm anticipating that btree_gist will become more
important, so I'd like to know what bugs are holding it back.So, anything else come to mind? Or does btree_gist just need a good
review? Or have the problems been fixed?The thing I was complaining about in the referenced message is specific
to the inet opclass; it's unfair to make it sound like it's a generic
problem with btree_gist. And no, it's not been fixed AFAIK.
Sorry, I thought I remembered a few other comments but couldn't find
them in the archives. I must be mistaken.
Regards,
Jeff Davis