Skip site navigation (1) Skip section navigation (2)

Re: Performance Anomalies in 7.4.5

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>,Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Performance Anomalies in 7.4.5
Date: 2004-10-28 17:20:56
Message-ID: 1098984056.8557.637.camel@home (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, 2004-10-28 at 12:31, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)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?



In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2004-10-28 17:50:29
Subject: Re: Performance Anomalies in 7.4.5
Previous:From: Tom LaneDate: 2004-10-28 16:31:28
Subject: Re: Performance Anomalies in 7.4.5

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group