| From: | Ty Busby <tybusby(at)yahoo(dot)com> |
|---|---|
| To: | Ty Busby <tybusby(at)gmail(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: optimize self-join query |
| Date: | 2011-10-29 21:04:11 |
| Message-ID: | A6BD48AA-5E71-4310-986E-05E6BDC2328F@yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Thanks to everyone for all the thoughtful responses. They have been incredibly helpful.
Ended up optimizing per Lee, and creating buckets per Tom. Thanks again.
On Oct 25, 2011, at 2:37 PM, Ty Busby wrote:
I have a table that stores a very large starting number called epc_start_numeric and a quantity. I've apparently built the most inefficient query possible for doing the job I need: find out if any records overlap. Imagine the epc_start_numeric + quantity representing a block of numbers. I need to find out if any of these blocks overlap.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Bakuwel | 2011-10-29 21:16:54 | Re: Different order by behaviour depending on where clause? |
| Previous Message | Phil Couling | 2011-10-28 10:25:20 | Re: Different order by behaviour depending on where clause? |