From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | zxo102 ouyang <zxo102(at)gmail(dot)com> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to speed up the first-time-searching in pgsql? |
Date: | 2009-05-28 08:23:57 |
Message-ID: | 4A1E4A1D.90004@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
zxo102 ouyang wrote:
> Hi there,
> Thanks for your suggestions. I do have an application running on the machine
> all the time. In fact, the application keeps writing real-time monitoring
> data into the database. Based on my understanding of your messages, I can't
> do anything to speed up the first-time-searching. Probably I can give a
> waiting process bar to the users and let them wait for the results.
No, I think you missed the detail on some of the answers. There are
limitations (as discussed in the answers), but the simple suggestion in
the first answer will probably help a lot.
Set up a scheduled task to run a big search of the database an hour
before people start work. This can be as simple as a .BAT file running
"SELECT * FROM big_table" triggered by Windows' Task Scheduler.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2009-05-28 08:48:18 | Re: Postgres registry access using java |
Previous Message | Simon Riggs | 2009-05-28 08:14:44 | Re: What is the right way to deal with a table with rows that are not in a random order? |