From: | Dick Kniep <dick(at)kniep(dot)nl> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: B-tree performance improvements in 8.x |
Date: | 2006-02-08 00:07:21 |
Message-ID: | 200602080107.21691.dick@kniep.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi list,
Does this also affect if you have many NULL values in the key? So testing Not
is NULL would also be affected?
Cheers,
Dick Kniep
On Tuesday 07 February 2006 23:13, Tom Lane wrote:
> jao(at)geophile(dot)com writes:
> > Quoting Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> >> In 8.0, the descent code can do
> >> either "first entry >= X" or "first entry > X", and the positioning
> >> rules never need to step more than one entry to locate the desired
> >> starting position (details left as exercise for the reader).
> >
> > What about a compound index (x, y), in which there are many y values
> > for a given x? My query is "... WHERE x = ? and y = ?".
>
> Doesn't really matter whether the key is simple or compound --- all
> that matters is whether you have multiple entries that are "equal" to
> the boundary value.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
From | Date | Subject | |
---|---|---|---|
Next Message | Luki Rustianto | 2006-02-08 03:54:37 | Is there a way to limit CPU usage per user |
Previous Message | Christopher Browne | 2006-02-08 00:00:00 | Re: Clarification Regarding Vacuum and template1 |