Very Fast Version:
Recently my database stopped respecting one of my indexes, which took a query
that should run in subsecond response time and turning it into something that
with small data sets runs in the 7-10 minute range and with large data sets
runs in the 30 minute - eternity range.
On Wed, Nov 23, 2011 at 7:24 PM, Gary Warner g...@cis.uab.edu wrote:
See that Seq Scan on link_url? We can't figure out why that is there! We
should be scanning for a matching urlid and we have an index on urlid?
When this is happening in a two table version of this problem, we can get
Can you post your non-default postgresql.conf settings? (I'd hazard a
guess that you have effective_cache_size set to the default 128MB).
Best wishes
Mark
On 24/11/11 11:24, Gary Warner wrote:
Very Fast Version:
Recently my database stopped respecting one of my indexes, which took a query
Gary Warner g...@cis.uab.edu writes:
Recently my database stopped respecting one of my indexes, which took a query
that should run in subsecond response time and turning it into something
that with small data sets runs in the 7-10 minute range and with large data
sets runs in the 30 minute
