Hello,
I recently ran a vacuum analyze on the bundled HQDB (Postgres 8.1.2) on my HQ 4.0.2 installation and, after doing its thing, it came back with these log entries:
2009-02-22 22:00:02.823 ] LOG: number of page slots needed (20016) exceeds max_fsm_pages (20000)
2009-02-22 22:00:02.823 ] HINT: Consider increasing the configuration parameter "max_fsm_pages" to a value over 20016.
I went ahead and increased the max_fsm_pages value in the postgresql.conf to 20100 and restarted Postgres. Is this unique to my environment, or should this be something that everyone running HQ on a Postgres DB consider doing?
Brian
I recently ran a vacuum analyze on the bundled HQDB (Postgres 8.1.2) on my HQ 4.0.2 installation and, after doing its thing, it came back with these log entries:
2009-02-22 22:00:02.823 ] LOG: number of page slots needed (20016) exceeds max_fsm_pages (20000)
2009-02-22 22:00:02.823 ] HINT: Consider increasing the configuration parameter "max_fsm_pages" to a value over 20016.
I went ahead and increased the max_fsm_pages value in the postgresql.conf to 20100 and restarted Postgres. Is this unique to my environment, or should this be something that everyone running HQ on a Postgres DB consider doing?
Brian