From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsqlperform <pgsql-performance@postgresql.org>
Subject: Re: sudden drop in statement turnaround latency -- yay!.
Date: Mon, 03 Jan 2005 19:48:54 -0500
Message-ID: <11787.1104799734@sss.pgh.pa.us> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A758D@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A758D@Herge.rcsinc.local>
"Merlin Moncure" <merlin.moncure@rcsonline.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, merlin.moncure@rcsonline.com
Subject: Re: sudden drop in statement turnaround latency -- yay!.
In-Reply-To: <11787.1104799734@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox