Re: large tables and simple "= constant" queries using indexes

From: Bill Moran <wmoran(at)collaborativefusion(dot)com>
To: John Beaver <john(dot)e(dot)beaver(at)gmail(dot)com>
Cc: Gaetano Mendola <mendola(at)gmail(dot)com>, Pgsql-Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: large tables and simple "= constant" queries using indexes
Date: 2008-04-10 17:08:54
Message-ID: 20080410130854.f3a3f110.wmoran@collaborativefusion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

In response to John Beaver <john(dot)e(dot)beaver(at)gmail(dot)com>:

> Thanks Eric and Gaestano - interesting, and both examples of my naivite. :)
>
> I tried running large select(*) queries on other tables followed by another try at the offending query, and it was still fast. Just to be absolutely sure this is a scalable solution, I'll try restarting my computer in a few hours to see if it affects anything cache-wise.

I say this over and over again ... because I think it's really cool and
useful.

If you install the pg_buffercache addon, you can actually look into
PostgreSQL's internals and see what tables are in the buffer in real
time. If you're having trouble, it can (potentially) be a helpful
tool.

--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2008-04-10 18:47:59 Re: large tables and simple "= constant" queries using indexes
Previous Message John Beaver 2008-04-10 16:37:45 Re: large tables and simple "= constant" queries using indexes