| From: | "David Rees" <drees76(at)gmail(dot)com> |
|---|---|
| To: | "Nimesh Satam" <nimesh(dot)zedo(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, nsatam(at)zedo(dot)com, gauri(at)zedo(dot)com, vidhya <vidhya(at)zedo(dot)com> |
| Subject: | Re: insert and Update slow after implementing slony. |
| Date: | 2008-12-17 19:59:14 |
| Message-ID: | 72dbd3150812171159t28806112l6470ef1327a2e8eb@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Dec 16, 2008 at 8:03 PM, Nimesh Satam <nimesh(dot)zedo(at)gmail(dot)com> wrote:
> We are trying to implement slony as a replication tool for one of our
> database. The Insert and updates have increased by approximately double
> making some of our important script slow.
What version of PostgreSQL are you running and on what type of hardware?
I suspect that moving pg_log onto a separate spindle and/or upgrading
your RAID controller to something with a BBU and configured in
write-back mode would get most of your performance back.
If you aren't running PostgreSQL 8.3, that might also help update
performance significantly as well.
-Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2008-12-17 21:14:52 | Re: measure database contention |
| Previous Message | Scott Marlowe | 2008-12-17 18:57:33 | Re: measure database contention |