On Thu, Jun 28, 2012 at 12:12 PM, Alvaro Herrera
> The other question is whether such an index would prevent an update from
> being HOT when the non-indexed values are touched. That could be a
> significant difference.
I don't see Index-Only-Scans being something that will be used in
"high churn" tables.
So as long as the value of these "covering/included" fields is tied to
index-only scans, maybe it isn't a problem?
Of course, we have have a hard time convincing people that the "index
only" scans they want can't be "index only" because heap pages aren't
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
In response to
pgsql-hackers by date
|Next:||From: Josh Kupershmidt||Date: 2012-06-28 16:32:41|
|Subject: Re: pg_signal_backend() asymmetry|
|Previous:||From: Robert Haas||Date: 2012-06-28 16:23:05|
|Subject: Re: embedded list v2|