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

Re: Very big insert/join performance problem (bacula)

From: Marc Cousin <cousinmarc(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Very big insert/join performance problem (bacula)
Date: 2009-07-24 05:13:06
Message-ID: 200907240713.06926.cousinmarc@gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
> It really has very little impact.  It only affects index scans, and
> even then only if effective_cache_size is less than the size of the
> table.
>
> Essentially, when this kicks in, it models the effect that if you are
> index scanning a table much larger than the size of your cache, you
> might have to reread some blocks that you previously read in during
> *that same index scan*.


Ok, thanks for clearing that up for me. Still, I think the doc could be 
improved on this point (sorry to be a bit obsessed with that, but I'm one of 
the french translators, so I like the doc to be perfect :) )

In response to

Responses

pgsql-performance by date

Next:From: Albe LaurenzDate: 2009-07-24 06:14:23
Subject: Re: Configuring Postgresql for writing BLOB at a high-rate
Previous:From: Robert HaasDate: 2009-07-24 03:48:27
Subject: Re: Very big insert/join performance problem (bacula)

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