Tom Lane ha scritto:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Limit (50)
Sort (key: pse_lastlogin)
Result
Append
Limit (50)
SeqScan tbl_profile_search
Limit (50)
Indexscan tbl_profile_search_interest_1
Limit (50)
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Is this possible? It would be very fast.
It's possible but not exactly simple. As an example, your proposed
plan:
> Limit (50)
> Sort (key: pse_lastlogin)
> Result
>Append
> Limit (50)
>SeqScan tbl_profile_search
>
I followed up with Joshua on Jabber. This is the query:
SELECT pse_userid FROM tbl_profile_search WHERE pse_normalized_text='1'
and pse_interest_type = 10 order by pse_lastlogin DESC limit 50 offset 0
I suggested adding an index on (pse_normalized_text, pse_lastlogin), on
the assumption that th
Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>> Tom Lane wrote:
>>> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
We have a problem with CE that I want to verify is either expected
behavior, a bug or something else :).
>>> Uh, what's your problem exactly? The example only seems to demo
Joshua D. Drake wrote:
> Tom Lane wrote:
> > "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> >> We have a problem with CE that I want to verify is either expected
> >> behavior, a bug or something else :).
> >
> > Uh, what's your problem exactly? The example only seems to demonstrate
> > that if
Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> We have a problem with CE that I want to verify is either expected
>> behavior, a bug or something else :).
>
> Uh, what's your problem exactly? The example only seems to demonstrate
> that if you don't ask for a sort, you don't g
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> We have a problem with CE that I want to verify is either expected
> behavior, a bug or something else :).
Uh, what's your problem exactly? The example only seems to demonstrate
that if you don't ask for a sort, you don't get one.
