zxo102 ouyang wrote:
Hi all,
I have a table which has more than 10millions records in pgsql
which is running on window 2003. During night, nobody search the
database. In morning, when people start to the application, it will
take more than 30 seconds to get database back. After several times of
same searching, the results can be returned in 8 seconds.
Is this related to some kinds of process priority setting in
window 2003? If so, how do I set the pgsql processes in highest priority?
are there other applications running on this same server? my first
guess is, other programs are doing disk IO when the postgres database is
idle, and pushing the postgres stuff out of the in-memory cache.
Windows is pretty aggressive about reclaiming idle memory, and there's
not much you can do about it.
maybe schedule something to run in the AM shortly before the regular
database users show up which will do queries that force a full table
scan on each table, this will cause all the imporant data to swap back in.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
