Re: Minor inaccuracy in jsonb_path_ops documentation

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Minor inaccuracy in jsonb_path_ops documentation
Date: 2014-07-24 22:42:36
Message-ID: CAM3SWZSVQnieHi+56PPqGD+azt_H=9-LiFAN0txHJXGjZRLF2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 24, 2014 at 3:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The fact that the planner can avoid that in the presence of a
> simple constant comparison value doesn't make it a good idea to
> use jsonb_path_ops indexes if you do this type of query a lot,
> because in some usages the planner won't see a constant comparison
> value, and if so it'll likely choose an indexscan by default.

Well, with idiomatic usage a constant value generally will be used.
But I do see your point.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2014-07-24 23:16:38 Re: SKIP LOCKED DATA (work in progress)
Previous Message Andres Freund 2014-07-24 22:04:27 Re: Why does xlog.c not treat COMMIT_PREPARED/ABORT_PREPARED as commit/abort?