On 04/05/14 10:29, Jon Miller wrote:
That's another fine suggestion though I still believe the issues were/are still related to the actual SQL queries being ran. I completed my planned routine last evening but just recreating the DB and reloading my backup didn't change anything. I then changed the following PostgreSQL tunables: - shared_buffers from (default?) 32MB => 2048MB - work_mem from 1MB => 20MB - maintenance_work_mem from 16MB => 300MB
Did you `analyze` the database after reloading it? (If not, try it).
So, that's why I keep my attention on the DB. And now when I look for what queries are running, I keep seeing only this one:
Set log_min_duration to something (see http://www.postgresql.org/docs/8.4/static/runtime-config-logging.html) and reload the postgresql config (service postgresql reload).
Is there a common table in all of the queries being logged? Check indexes and so on.
Does PostgreSQL use pgsql_tmp space when queries can not be performed within working memory?
Yes. -- Postgresql & php tutorials http://www.designmagick.com/ _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
