Dear Folks, On 24/07/07 05:31 +1000, Nick Urbanik wrote:
Dear Jim,On 15/05/07 20:28 -0500, Jim C. Nasby wrote:On Wed, May 16, 2007 at 11:20:52AM +1000, Nick Urbanik wrote:Dear Alvaro, On 15/05/07 21:12 -0400, Alvaro Herrera wrote: >Nick Urbanik wrote: >>On 15/05/07 18:53 -0400, Alvaro Herrera wrote: >You probably need to better configure the FSM settings. See >fsm_max_pages in the docs. This is probably the critical piece of information we need to prevent the need for another sleepless night and an outage! Thank you.http://www.pervasive-postgres.com/instantkb13/article.aspx?id=10087&cNode=5K1C3W might be of use as well.I have not been able to find this page; pervasive have moved their site around. Any keywords in this article I can google for to find the new URL?
Thanks: I found a cache of the article, which is entitled, "Q10087 - INFO: Is PostgreSQL remembering what you vacuumed?" http://72.14.253.104/search?q=cache:n_LQiTbm9joJ:www.pervasivepostgres.com/instantkb13/article.aspx%3Fid%3D10087+%22Is+PostgreSQL+remembering+what+you+vacuumed%3F%22&hl=en&ct=clnk&cd=2&gl=au A simplistic summary is to do a full, verbose vacuum of the entire postgresql installation (of all the databases together), and then the last two lines contain output about FSM utilisation. The values of max_fsm_relations and max_fsm_pages should then be set in postgresql.conf in light of this information. -- Nick Urbanik RHCE http://nicku.org [EMAIL PROTECTED] GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
pgp4VGyF4DWfK.pgp
Description: PGP signature
