Matthew Wakeling <matthew@xxxxxxxxxxx> writes: > On Thu, 16 Apr 2009, Tom Lane wrote: >> Also, what are the physical sizes of the two indexes? > location_object_start_gist | 193 MB > location_object_start | 75 MB >> I notice that the inner nestloop join gets slower too, when it's not >> changed at all --- that suggests that the overall I/O load is a lot >> worse, so maybe the reason the query is falling off a performance cliff >> is that the GIST index fails to fit in cache. > Memory in the machine is 16GB. Hmm, and what is shared_buffers set to? How big are the tables and other indexes used in the query? We still have to explain why the inner nestloop got slower, and it's hard to see that unless something stopped fitting in cache. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
