From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | Preeti Khurana <preeti(dot)khurana(at)globallogic(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres's Performance degrades after heavy db operation |
Date: | 2009-06-08 16:28:29 |
Message-ID: | 2f4958ff0906080928m27538332q78a6e97671107d83@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 8, 2009 at 2:38 PM, Preeti
Khurana<preeti(dot)khurana(at)globallogic(dot)com> wrote:
> Hi,
>
> I am using Postgresql 8.1.2 and performing quite a huge number of db
> operations ( insert/update/ delete) in around 4 tables. Around 3 million of
> db is inserted and then 600 K rows are updated for around 5-6 times during a
> day. Its observed that running this process for few days ( 5-6 days) makes
> the db access quite slower. Auto-Vacuum is set to ON with other parameters
> set to default.
>
>
>
> Slony 1.1.5 is being used for the db replication simultaneously.
>
>
>
> Any ideas/pointers on what could be making the DB slow after all these heavy
> operations being performed?
check if vacuum analyze says anythihing about FSM size being too small.
--
GJ
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-06-08 16:28:35 | Re: Sum of multiplied deltas |
Previous Message | Rob Sargent | 2009-06-08 16:26:05 | 'cost' and 'rows' for volitile function |