Re: Allowing GIN array_ops to work on anyarray

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Enrique Meneses <emmeneses(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Allowing GIN array_ops to work on anyarray
Date: 2016-09-26 13:27:31
Message-ID: 28608.1474896451@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Enrique Meneses <emmeneses(at)gmail(dot)com> writes:
> I was not sure what "Spec compliant means"... so I did not select as tested or passed. What should I do to validate that this change is "Spec compliant"?

It's irrelevant to this patch, AFAICS. The SQL standard doesn't discuss
indexes at all, much less legislate on which operator classes ought to
exist for GIN indexes.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-09-26 13:33:31 Re: VACUUM's ancillary tasks
Previous Message Ryan Murphy 2016-09-26 12:57:42 Re: proposal: psql \setfileref