From: | "Sachin Kumar" <Sachin(dot)Ku(at)globallogic(dot)com> |
---|---|
To: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Performance issues with postgresql-8.4.0 |
Date: | 2010-06-29 07:01:18 |
Message-ID: | 21026437C2BC0D45BE196CB0A35EFEFD052700D7@ex2-del1.synapse.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
We are using postgresql-8.4.0 on 64-bit Linux machine (open-SUSE 11.x).
It's a master/slave deployment & slony-2.0.4.rc2 is used for DB
replication on the slave box.
At times we have observed that postgres stops responding for several
minutes, even couldn't fetch the number of entries in a particular
table. One such instance happens when we execute the following steps:
- Add few lakh entries (~20) to table X on the master DB.
- After addition, slony starts replication on the slave DB. It
takes several minutes (~25 mins) for replication to finish.
- During this time (while replication is in progress), sometimes
postgres stops responding, i.e. we couldn't even fetch the number of
entries in any table (X, Y, etc).
Can you please let us know what could the reason for such a behavior and
how it can be fixed/improved.
Regards,
Sachin
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-06-29 10:52:10 | Re: PostgreSQL as a local in-memory cache |
Previous Message | Bruce Momjian | 2010-06-28 21:57:25 | Re: PostgreSQL as a local in-memory cache |