Skip site navigation (1) Skip section navigation (2)

Re: LIKE, leading percent, bind parameters and indexes

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>,Rodrigo Hjort <rodrigo(dot)hjort(at)gmail(dot)com>,Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: LIKE, leading percent, bind parameters and indexes
Date: 2006-05-28 21:25:45
Message-ID: 20060528212545.GD22869@svana.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sun, May 28, 2006 at 10:43:18PM +0300, Heikki Linnakangas wrote:
> I don't know the planner internals, so this might not make any sense at 
> all, but how about having separate index scan and fetch nodes. Index scan 
> would return index tuples and fetch would get the corresponding heap 
> tuples. You could then have whatever you want between them, perhaps 
> deferring the fetch step until just before returning the rows to the 
> client.

That's kinda what a bitmap scan does. Although, we never fetch tuples
unless you're going to use the result in some way...

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog(at)svana(dot)org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-05-28 21:53:07
Subject: Re: LIKE, leading percent, bind parameters and indexes
Previous:From: David FetterDate: 2006-05-28 20:13:50
Subject: Re: COPY FROM view

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group