From: | Sebastian Hennebrueder <usenet(at)laliluna(dot)de> |
---|---|
To: | |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: tricky query |
Date: | 2005-06-28 20:38:54 |
Message-ID: | 42C1B55E.40405@laliluna.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
John A Meinel schrieb:
> John A Meinel wrote:
>
>>
>
> Well, I was able to improve it to using appropriate index scans.
> Here is the query:
>
> SELECT t1.id+1 as id_new FROM id_test t1
> WHERE NOT EXISTS
> (SELECT t2.id FROM id_test t2 WHERE t2.id = t1.id+1)
> ORDER BY t1.id LIMIT 1;
>
> I created a test table which has 90k randomly inserted rows. And this is
> what EXPLAIN ANALYZE says:
>
>
As Cosimo stated the result can be wrong. The result is always wrong
when the id with value 1 does not exist.
--
Best Regards / Viele Grüße
Sebastian Hennebrueder
----
Tutorials for JSP, JavaServer Faces, Struts, Hibernate and EJB
Get support, education and consulting for these technologies - uncomplicated and cheap.
From | Date | Subject | |
---|---|---|---|
Next Message | Billy extyeightysix | 2005-06-28 20:39:05 | optimized counting of web statistics |
Previous Message | Merlin Moncure | 2005-06-28 19:45:53 | Re: tricky query |