Re: Functional index adding one - Mailing list pgsql-general

From Tom Lane
Subject Re: Functional index adding one
Date
Msg-id 2693.1215097886@sss.pgh.pa.us
Whole thread Raw
In response to Re: Functional index adding one  (Sam Mason <sam@samason.me.uk>)
Responses Re: Functional index adding one
List pgsql-general
Sam Mason <sam@samason.me.uk> writes:
> You just want an extra set of brackets; i.e.:

>   CREATE INDEX token_position_func ON token ((position+1));

> Should do the trick.  Not entirely sure why, but it'll probably have
> something to do with avoiding ambiguity in the grammar.

Right.  The problem is the Berkeley-era decision to put index opclasses
into the syntax without any keyword or punctuation, viz

    create index ... on table (column_name [ opclass_name ]);

So something like

    CREATE INDEX token_position_func ON token (a + b);

is ambiguous: is the + an infix operator, or is it a postfix operator
and the "b" is to be taken as an opclass name?

We hacked around that by requiring parens around expressions.  For
backwards compatibility with other Berkeley-era syntax, there's
a special exception that you can omit the parens when the expression is
just a function call.

            regards, tom lane

pgsql-general by date:

Previous
From: Csaba Nagy
Date:
Subject: Re: Switching between terminals
Next
From: "Valter Douglas Lisbôa Jr."
Date:
Subject: High inserting by syslog