Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 76E879FB6C2 for ; Thu, 7 Jun 2007 22:31:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 12068-06 for ; Thu, 7 Jun 2007 22:31:21 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A0F019FB63F for ; Thu, 7 Jun 2007 22:31:21 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l581VEGX011711; Thu, 7 Jun 2007 21:31:14 -0400 (EDT) To: Alvaro Herrera cc: Steven Flatt , "Steinar H. Gunderson" , pgsql-performance@postgresql.org Subject: Re: performance drop on 8.2.4, reverting to 8.1.4 In-reply-to: <20070608012257.GB20828@alvh.no-ip.org> References: <20070518104646.GA13811@uio.no> <008201c7993c$76c88a10$653e10ac@ilgvaio> <20070518111455.GA13978@uio.no> <28604.1179503689@sss.pgh.pa.us> <357fa7590706051430h5db6760dx9d4a46c7a8a36205@mail.gmail.com> <10645.1181081285@sss.pgh.pa.us> <357fa7590706071011g4e337937rc622ffed39856425@mail.gmail.com> <11349.1181265079@sss.pgh.pa.us> <20070608012257.GB20828@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Thu, 07 Jun 2007 21:22:57 -0400" Date: Thu, 07 Jun 2007 21:31:14 -0400 Message-ID: <11710.1181266274@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/148 X-Sequence-Number: 25181 Alvaro Herrera writes: > Tom Lane escribió: >> I was hoping that the auto plan invalidation code in CVS HEAD would get >> it out of this problem, but it seems not to for the problem-as-given. >> The trouble is that it won't change plans until autovacuum analyzes the >> tables, and that won't happen until the transaction commits and sends >> off its I-inserted-lotsa-rows report to the stats collector. > I think there is something we can do about this -- drop the default > value for analyze threshold. Maybe worth doing, but it doesn't help for Steve's example. regards, tom lane