From: Rod Taylor <pg@rbt.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Performance Anomalies in 7.4.5
Date: Thu, 28 Oct 2004 13:20:56 -0400
Message-ID: <1098984056.8557.637.camel@home> (raw)
In-Reply-To: <2815.1098981088@sss.pgh.pa.us>
References: <20041028080109.E47A83A4828@svr1.postgresql.org>
<200410280907.00445.josh@agliodbs.com>
<2815.1098981088@sss.pgh.pa.us>
On Thu, 2004-10-28 at 12:31, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
> >> One drawback to this is that it would require an additional lseek per table
> >> while planning, but that doesn't seem like a huge penalty.
>
> > Hmmm ... would the additional lseek take longer for larger tables, or would it
> > be a fixed cost?
>
> Should be pretty much a fixed cost: one kernel call per table.
Is this something that the bgwriter could periodically do and share the
data? Possibly in the future it could even force a function or prepared
statement recompile if the data has changed significantly?
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: pg@rbt.ca, tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Performance Anomalies in 7.4.5
In-Reply-To: <1098984056.8557.637.camel@home>
* 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