On Fri, Jul 21, 2006 at 07:41:02 +0000,
Alaa El Gohary <alaaelgohary(at)bftech(dot)com(dot)eg> wrote:
> The following bug has been logged online:
The report below isn't a bug, its a performance question and should have
been sent to pgsql-performance(at)postgresql(dot)org(dot) I am redirecting replies there.
> A query on the postgresql DB takes about 5 seconds and then it starts to
> take more time till it reaches about 60 seconds by the end of the same day.
> I tried vacuum but nothing changed the only thing that works is to dump the
> DB ,drop and create a new one with the dump taken.
> i need to know if there is any way to restore the performance back without
> the need for drop and create
> cause i can't do this accross the day
You most likely aren't vacuuming often enough and/or don't have your FSM
setting high enough.
In response to
pgsql-performance by date
|Next:||From: Kevin Keith||Date: 2006-07-21 19:17:38|
|Subject: Partitioned tables in queries|
|Previous:||From: Kevin McArthur||Date: 2006-07-21 18:15:28|
|Subject: Bad Planner Statistics for Uneven distribution.|
pgsql-bugs by date
|Next:||From: John Gray||Date: 2006-07-22 13:31:03|
|Subject: Re: BUG #2541: XML2 module: odd query results|
|Previous:||From: Tino Schwarze||Date: 2006-07-21 12:30:55|
|Subject: initdb problem on Windows - SOLVED|