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

by john.e.beaver@[EMAIL PROTECTED] (John Beaver) Apr 10, 2008 at 12:37 PM

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks Eric and Gaestano - interesting, and both examples of my
naivite. :)<br>
<br>
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.<br>
<br>
<br>
Gaetano Mendola wrote:
<blockquote cite="mid:47FE3DC7.4010700@[EMAIL PROTECTED]
" type="cite">
  <pre wrap="">John Beaver wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">- Trying the same constant a second time gave an
instantaneous result,
I'm guessing because of query/result caching.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
AFAIK no query/result caching is in place in postgres, what you are
experiencing
is OS disk/memory caching.


Regards
Gaetano Mendola


  </pre>
</blockquote>
</body>
</html>

15 Posts in Topic:

large tables and simple "= constant" queries using indexes

john.e.beaver@[EMAIL PROT

2008-04-09 16:58:27

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

acmmailing@[EMAIL PROTECT

2008-04-09 23:21:20

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

acmmailing@[EMAIL PROTECT

2008-04-10 09:13:39

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

lists@[EMAIL PROTECTED]