| From: | Herouth Maoz <herouth(at)unicell(dot)co(dot)il> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Adding more space, and a vacuum question. |
| Date: | 2011-01-30 16:14:25 |
| Message-ID: | 06D135DE-B482-4161-9C5B-16652886085D@unicell.co.il |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 30/01/2011, at 12:27, Craig Ringer wrote:
>
> OK, so you're pre-8.4 , which means you have the max_fsm settings to play with. Have you seen any messages in the logs about the free space map (fsm)? If your install didn't have a big enough fsm to keep track of deleted tuples, you'd face massive table bloat that a regular vacuum couldn't fix.
Ouch. You're absolutely right. There are messages about max_fsm_pages in the postgres log. It's currently set to 153600. According to the documentation, I can increase it up to 200000. Will that even help? How do I find out how many I need to set it to?
>
> You also don't have the visibility map, which means that (auto)vacuum can't skip bits of the tables it knows don't need vacuuming. Your vacuums will be slower.
>
> Autovacuum improved significantly in both 8.4 and 9.0; consider an upgrade.
I will consider it. Thank you.
Herouth
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Warner | 2011-01-30 16:35:47 | Re: Full Text Index Scanning |
| Previous Message | Andrew Sullivan | 2011-01-30 16:00:49 | Re: Adding more space, and a vacuum question. |