From: | Charles Sheridan <cesheri(at)swbell(dot)net> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Automatic Index Creation for Column Types |
Date: | 2013-08-19 14:09:16 |
Message-ID: | 5212270C.1040502@swbell.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Agree, these are significant concerns. Just to make sure the scope of
the proposal is clear, I'm referring to col types created via CREATE
TYPE, i.e. locally-defined col types of much tighter granularity than
standard col types like INTEGER. Locally, one could adopt a naming
convention for these cols to identify that they have auto-generated
indices.
Best, Charles
On 13-08-19 8:42 AM, Andrew Dunstan wrote:
>
> On 08/19/2013 09:10 AM, Charles Sheridan wrote:
>> Hi,
>>
>> I don't see indication that the capability described below exists in
>> Postgres (or any RDBMS), so this is likely a feature request --
>>
>> For column types that are frequently defined in tables, and which are
>> typically indexed, it would be helpful to be able to specify in the type
>> definition of the column that its addition/creation into a table should
>> be automatically accompanied by the creation of an associated index.
>>
>> Auto-index generation for a specific column type would be overridable
>> for specific tables, as you wouldn't always want to auto-create an index
>> at the time of column addition to a table. In the case of CREATE TABLE,
>> this would be less of a concern, and more of a concern for ALTER TABLE
>> ADD COLUMN.
>>
>> Such a configuration would also specify the type of index.
>>
>> What do you think ?
>>
>>
>>
>
>
> I think it's a bad idea. Indexes are not free and it would be a huge
> and unwarranted assumption that they are wanted just because some
> column type is used. If you want indexes it's up to you to create
> them. The only exception is when they are created as an implementation
> artifact for a table constraint, but even then you have to express the
> constraint, it's not just assumed.
>
> cheers
>
> andrew
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2013-08-19 14:11:01 | Re: Fix Windows socket error checking for MinGW |
Previous Message | Michael Cronenworth | 2013-08-19 13:52:58 | Re: Fix Windows socket error checking for MinGW |