From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Deprecating Hash Indexes |
Date: | 2012-10-19 09:16:53 |
Message-ID: | CA+U5nMJjtzo=hUv7c8BWX=QTdvtiLNtS_d+QUdo1O5oFDhH=Hw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16 October 2012 04:49, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On Mon, 2012-10-15 at 11:14 -0700, Josh Berkus wrote:
>> I'd be in favor of a warning on create index.
>
> Only if you can turn it off, please.
>
> But I don't think a warning is appropriate if the statement does exactly
> what the user wanted. The place to point out shortcomings of the
> implementation is in the documentation.
Fair comment. I've just added a caution in the docs.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2012-10-19 10:02:29 | Re: [v9.3] Row-Level Security |
Previous Message | Simon Riggs | 2012-10-19 09:10:23 | Re: Bugs in CREATE/DROP INDEX CONCURRENTLY |