From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Deprecating Hash Indexes |
Date: | 2012-10-15 17:36:06 |
Message-ID: | 20121015173606.GP1583@aart.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Oct 15, 2012 at 10:13:24AM -0400, Robert Haas wrote:
> On Sun, Oct 14, 2012 at 9:45 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> > * Put WARNINGs in the docs against the use of hash indexes, backpatch
> > to 8.3. CREATE INDEX gives no warning currently, though Index Types
> > does mention a caution.
>
> I'd be in favor of adding such warnings to the documentation if they
> are not there already, and possibly even warning on CREATE INDEX ..
> USING hash(). I don't think I'd go so far as to say that we should
> imply that they'll be removed in a future release. Given how deeply
> intertwined they are with the planner, I doubt that that will happen;
> and I think there is enough interest in the technology that it's
> likely to eventually be fixed.
>
+1 for adding more warnings but do not deprecate them.
Regards,
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2012-10-15 17:40:48 | Re: pg_stat_lwlocks view - lwlocks statistics, round 2 |
Previous Message | Simon Riggs | 2012-10-15 17:26:43 | Re: Deprecating Hash Indexes |