On Jan 30, 2006, at 12:28 AM, Ron Marom wrote:
First of all thanks for you quick and efficient response.
Indeed I forgot to mention that I AM vacuuming the database using a
daemon every few hours; however this seems not to be the issue this
time, as when the CPU consumptions went up I tried to
"Ron Marom" <[EMAIL PROTECTED]> writes:
> Indeed I forgot to mention that I AM vacuuming the database using a
> daemon every few hours; however this seems not to be the issue this
> time, as when the CPU consumptions went up I tried to vacuum manually
> and this seemed to take no affect.
This is n
On Mon, Jan 30, 2006 at 09:28:14AM +0200, Ron Marom wrote:
> Indeed I forgot to mention that I AM vacuuming the database using a
> daemon every few hours; however this seems not to be the issue this
> time, as when the CPU consumptions went up I tried to vacuum manually
> and this seemed to take no
performace degrading after a while
On Mon, Jan 30, 2006 at 09:02:24AM +0200, Ron Marom wrote:
> I seem to have a problem with postgresql 7.4.2 running on Red Hat
> Enterprise Linux ES3.
If you can't upgrade to 8.0 or 8.1 then at least consider using the
latest version in the 7.4 bra
On Mon, Jan 30, 2006 at 09:02:24AM +0200, Ron Marom wrote:
> I seem to have a problem with postgresql 7.4.2 running on Red Hat
> Enterprise Linux ES3.
If you can't upgrade to 8.0 or 8.1 then at least consider using the
latest version in the 7.4 branch (7.4.11). You're missing almost
two years of
