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

Re: Confusing Query Performance

From: Matthew Wakeling <matthew(at)flymine(dot)org>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Confusing Query Performance
Date: 2008-10-01 10:49:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Wed, 1 Oct 2008, Gauri Kanekar wrote:
> "new_table1" is 18% of the the whole "table1".

>    ->  Nested Loop  (cost=186.26..647160.32 rows=42543 width=16) (actual time=655.832..6622.011 rows=5120582 loops=1)

>    ->  Nested Loop  (cost=0.00..414246.81 rows=25155 width=16) (actual time=19.578..4922.680 rows=5120582 loops=1)

The new table may be that much smaller than the old table, but you're 
selecting exactly the same amount of data from it. The data is fetched by 
indexes, which means random access, so the overall size of the data that 
you don't fetch doesn't make any difference.


Existence is a convenient concept to designate all of the files that an
executable program can potentially process.   -- Fortran77 standard

In response to

pgsql-performance by date

Next:From: Richard HuxtonDate: 2008-10-01 11:36:48
Subject: Re: dedicated server & postgresql 8.1 conf tunning
Previous:From: Gauri KanekarDate: 2008-10-01 10:34:28
Subject: Confusing Query Performance

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