Horton

Re: [PATCH] Opclass parameters

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nikita Glukhov <n.gluhov@postgrespro.ru>, Nikolay Shaplov <dhyan@nataraj.su>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Oleg Bartunov <obartunov@gmail.com>
Date: 2018-12-06T16:58:06Z
Lists: 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

Commits

  1. Documentation corrections for opclass parameters

  2. Implement operator class parameters