| From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
|---|---|
| To: | Benjamin Arai <benjamin(at)araisoft(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problem with large table not using indexes (I think) |
| Date: | 2006-12-23 19:39:56 |
| Message-ID: | Pine.LNX.4.64.0612231138370.6126@discord.home.frostconsultingllc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Sat, 23 Dec 2006, Benjamin Arai wrote:
> The largest table in my database (30GB) has mysteriously went from taking
> milli-seconds to perform a query to minutes. This disks are fine and I have
> a 4GB shared_memory. Could this slow down have to do with the fsm_max_pages
> or something else like that? I made it larger but the queries still taking a
> long time. I do daily vacuum's but I don't run it with -z or --full. I
> would like to avoid doing a --full if possible because it would literally
> take over a week to complete. Any help would be greatly appreciated.
Benjamin,
When is the last time you ran ANALYZE? That's what the -z option does. If
you're only vacuuming once daily, you should definitely analyze with the -z
flag as well.
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Arai | 2006-12-23 19:41:48 | Re: Problem with large table not using indexes (I think) |
| Previous Message | A. Kretschmer | 2006-12-23 19:33:39 | Re: Problem with large table not using indexes (I think) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Arai | 2006-12-23 19:41:48 | Re: Problem with large table not using indexes (I think) |
| Previous Message | Kurapica | 2006-12-23 19:34:49 | Does pgsql's regex processor optimize Common-Prefix? |