X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 694543A3CBE for ; Tue, 4 Jan 2005 00:49:16 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 10555-05 for ; Tue, 4 Jan 2005 00:48:56 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3051A3A3C6C for ; Tue, 4 Jan 2005 00:48:55 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j040mtWj011788; Mon, 3 Jan 2005 19:48:55 -0500 (EST) To: "Merlin Moncure" Cc: "pgsqlperform" Subject: Re: sudden drop in statement turnaround latency -- yay!. In-reply-to: <6EE64EF3AB31D5448D0007DD34EEB3412A758D@Herge.rcsinc.local> References: <6EE64EF3AB31D5448D0007DD34EEB3412A758D@Herge.rcsinc.local> Comments: In-reply-to "Merlin Moncure" message dated "Mon, 03 Jan 2005 16:11:44 -0500" Date: Mon, 03 Jan 2005 19:48:54 -0500 Message-ID: <11787.1104799734@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/32 X-Sequence-Number: 9722 "Merlin Moncure" writes: > Tom Lane wrote: >> Add a small cost factor to ensure we >> prefer materializing the smaller input. This changes several >> regression test plans, but with any luck we will now have more >> stability across platforms. > No. The planner is not a factor. You are missing the point: the possible change in a generated plan could be a factor. >> Change planner to use >> the current true disk file size as its estimate of a relation's >> number of blocks, rather than the possibly-obsolete value in >> pg_class.relpages. > doesn't seem like this would apply. Same point. Unless you have done EXPLAINs to verify that the same plans were used before and after, you can't dismiss this. >> * src/backend/utils/cache/relcache.c: Avoid scanning the >> relcache >> during AtEOSubXact_RelationCache when there is nothing to do, >> which >> is most of the time. This is another simple improvement to cut >> subtransaction entry/exit overhead. > Not clear from the comments: does this apply to every transaction, or > only ones with savepoints? If all transactions, it's a contender. It only applies to subtransactions, ie something involving savepoints. regards, tom lane