From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: max_fsm_relations |
Date: | 2009-02-27 21:16:21 |
Message-ID: | 20090227161621.9fe60357.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>:
> Ya, most of it's system stuff. OK, I see where the 1000 comes from. I bumped it up to 1200 in postgresql.conf. Is there a way I can spin that in without rebooting the DB (and kicking my user off)?
No. Unless something has changed that I'm not aware of, you have to do
a restart for PG to change that value, as it allocates the memory on
startup.
Unless you're expecting a considerable amount of table bloat in the
near future, you can just reset the value, then schedule the server
to restart during your next off-peak time. The server's not going to
meltdown immediately (unless you've got a _TON_ of update activity)
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-02-27 21:19:20 | Re: max_fsm_relations |
Previous Message | Gauthier, Dave | 2009-02-27 21:06:32 | Re: max_fsm_relations |