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

Re: I/O on select count(*)

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: I/O on select count(*)
Date: 2008-05-15 03:03:37
Message-ID: Pine.GSO.4.64.0805142254080.10990@westnet.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, 15 May 2008, Pavan Deolasee wrote:

> I had suggested in the past that whenever we set hint bits for a tuple, 
> we should check all other tuples in the page and set their hint bits too 
> to avoid multiple writes of the same page. I guess the idea got rejected 
> because of lack of benchmarks to prove the benefit.

From glancing at http://www.postgresql.org/docs/faqs.TODO.html I got the 
impression the idea was to have the background writer get involved to help 
with this particular situation.  The way things are setup right now, I 
would guess it's impractical for an individual client to be forced to wait 
for all the tuples in a block to be checked just because it ran into one 
tuple that needed its hint bits refreshed.

If the pages that had any hint bit updates since they were read/created 
were made easy to identify (maybe they already are), the writer could do 
the kind of scan you suggest anytime it was about to evict that page. 
That wouldn't be in the client's critical path and it would maximize the 
possible improvement here.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Responses

pgsql-performance by date

Next:From: Joshua D. DrakeDate: 2008-05-15 03:13:30
Subject: Re: I/O on select count(*)
Previous:From: Luke LonerganDate: 2008-05-15 02:52:01
Subject: Re: I/O on select count(*)

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