Re: [PATCH] Opclass parameters - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] Opclass parameters
Date
Msg-id CA+TgmoYU91G_8Sf59wUo-vSCFhbeBXuVQ7FTch6MuQ3fRe8WUg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Opclass parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Opclass parameters  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On Thu, Dec 6, 2018 at 11:55 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> How about saying that you must give an opclass name if you want to
> specify options, ie the syntax is
>
>         [ opclass_name [ ( options... ) ] ]
>
> I'm not necessarily wedded to that, but it seems worth throwing
> out the idea.

Agreed, that's not bad, certainly better than making OPTIONS more reserved.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: proposal: plpgsql pragma statement
Next
From: "Jonah H. Harris"
Date:
Subject: Re: proposal: plpgsql pragma statement