Re: [PROPOSAL][PROTOTYPE] Individual options for each index column: Opclass options

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Nikolay Shaplov <n(dot)shaplov(at)postgrespro(dot)ru>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PROPOSAL][PROTOTYPE] Individual options for each index column: Opclass options
Date: 2016-09-16 14:18:35
Message-ID: CA+TgmobHvZR=Oy0QrZfzya37h8g_wauzsPH6d4xGai+371Zv2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 24, 2016 at 10:06 AM, Nikolay Shaplov
<n(dot)shaplov(at)postgrespro(dot)ru> wrote:
> So adding options for opclass seems to be really good idea.
> To see how it works you should do the following:
>
> # create extension intarray ;
> # create table test (i int[]);
> # create table test2 (i int[]);
> # create index ON test USING GIST (i USING gist__intbig_ops WITH OPTIONS
> (sig_len_int=22) );
> # create index ON test2 USING GIST (i USING gist__intbig_ops WITH OPTIONS
> (sig_len_int=120) );

I think supporting syntax of this type would be a good idea.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Ignatov 2016-09-16 15:18:04 Re: Parallel sec scan in plpgsql
Previous Message Tom Lane 2016-09-16 14:11:12 Re: Why postgres take RowExclusiveLock on all partition