| From: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
|---|---|
| To: | Bogdan Matei <bogdan(at)in-consulting(dot)net> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1660: Growing used memory and critical performance loss |
| Date: | 2005-05-11 20:44:29 |
| Message-ID: | 20050511204429.GB10281@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, May 11, 2005 at 04:56:28PM +0100, Bogdan Matei wrote:
> These are the efects. First of all we thought that is our application that
> consumes all the performance of Postgresql, with a predilection in the peak
> time of traffic, we improved it very well but even so there is no change.
> What is weird is that the only solution that we found is to reconfigure and
> recreate the database at every 2-3 days. When is imediately created the
> memory used is about 180MB then it constantly grows.
The question that jumps at me is, what is your vacuum strategy?
--
Alvaro Herrera (<alvherre[a]surnet.cl>)
"World domination is proceeding according to plan" (Andrew Morton)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steven Mooij | 2005-05-11 23:33:08 | BUG #1662: Table constrains are not properly inherited. |
| Previous Message | Andrew - Supernews | 2005-05-11 20:27:12 | Re: Bug Report with Postgres 7.4 on AIX 5.3 |