| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | John Cole <john(dot)cole(at)uai(dot)com>, "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Out of memory on vacuum analyze |
| Date: | 2007-02-21 02:51:19 |
| Message-ID: | 51C436F6-C357-4462-9BD2-BFCEF93DE18E@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Feb 19, 2007, at 1:19 PM, Jeff Davis wrote:
> You told PostgreSQL that you have 900MB available for
> maintenance_work_mem, but your OS is denying the request. Try
> *lowering*
> that setting to something that your OS will allow. That seems like an
> awfully high setting to me.
900MB isn't that unreasonable if you're building indexes on a restore
or something similar. I have run into issues when trying to set it
much over 1G, though... on various OSes and platforms.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dave crane | 2007-02-21 03:02:36 | number of tables limited over time (not simultaneous)? |
| Previous Message | Robert Haas | 2007-02-21 02:36:58 | Re: complex referential integrity constraints |