Re: index question

From: "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: index question
Date: 2016-05-02 01:18:13
Message-ID: CAE_gQfWnB5z7WJnbyOHJUi8PtkaprpmeouL1tjbJNO=p5Bi6qg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> To clarify, the index is based on a function called "split_part(....)
> The WHERE clause is only referencing the full_part column, so the planner
> cannot associate the index with the full_part column.
>

Thanks for the explanation, Melvin.

It would be simple like:

CREATE INDEX CONCURRENTLY ON gorfs.inode_segments USING btree ("full_path");

?

Thanks again.
Lucas

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2016-05-02 01:51:01 Re: index question
Previous Message Melvin Davidson 2016-05-01 22:39:49 Re: index question