On Fri, Nov 30, 2012 at 5:22 AM, Henry Drexler <alonup...@gmail.com> wrote: > Hello, and thank you in advance. > > > Beyond the date vs timestamp troubleshooting I did, I am not sure what else > to look for, I know the increase of rows will have some affect but I just > don't think the query should go from 4 minutes to over 50.
If the doubling of the size causes it to exceed the cache, when before it did not, that could easily explain it. ... > and > massive.dateof <@ '(2012-07-22 17:00:00,2012-07-29 17:00:00]'::tsrange; I don't think the <@ can use the btree index, but if you wrote it as a "BETWEEN" it could. > With a query plan of: > "Index Scan using customer_id_sourcee on massive_m (cost=0.00..113.98 > rows=1 width=28)" Can you report the EXPLAIN (ANALYZE, BUFFERS) instead? Cheers, Jeff -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
