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