| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Vivek_Sharan <Vivek_Sharan(at)infosys(dot)com> |
| Cc: | "Guido Barosio" <gbarosio(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Heavy postgres process |
| Date: | 2008-09-17 14:43:26 |
| Message-ID: | dcc563d10809170743v41ea538chbf7989c95b9ec342@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Sep 17, 2008 at 7:18 AM, Vivek_Sharan <Vivek_Sharan(at)infosys(dot)com> wrote:
> Yes that's true and that's planned. We will migrate to Oracle. But as of now need some pointers on solving the problem in hand.
Well, updating to the latest 7.4 version would be a very very good
move. There are some very real and nasty data loss bugs in 7.4.5.
It's an in place update that requires only a few minutes of downtime.
I would guess you've got something like sort_mem set too high.
P.s. If you think PostgreSQL is hard to troubleshoot, I can't wait to
see you running Oracle.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Valentin Bogdanov | 2008-09-17 15:44:29 | Re: unable to backup database -- psql not up to date |
| Previous Message | Jonathan Nalley | 2008-09-17 14:23:23 | Re: unable to backup database -- psql not up to date |