Re: slower every day

From: "Michael Paesold" <mpaesold(at)gmx(dot)at>
To: <gbarosio(at)uolsinectis(dot)com(dot)ar>, <pgsql-performance(at)postgresql(dot)org>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: slower every day
Date: 2004-09-01 14:28:15
Message-ID: 01ae01c4902f$ed692490$ad01a8c0@zaphod
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-performance

This issue was resently discussed on hackers. It is a known issue, not very
convinient for the user. Nevertheless it is not fixed in 8.0, but will
perhaps be addressed in the next major release.
(Remembering, it was a non-trivial thing to change.)

Best Regards,
Michael Paesold

G u i d o B a r o s i o wrote:

> The solution appeared as something I didn't know
>
> On the .conf file
>
> Previous situation:
>
> #log_something=false
> log_something=true
>
> Worst situation
> #log_something=false
> #log_something=true
>
> Nice situation
> log_something=false
> #log_something=true
>
>
> Ok, the problem was that I assumed that commenting a value on
> the conf file will set it up to a default (false?). I was wrong.
> My server was writting tons of log's.
>
> Is this the normal behavior for pg_ctl reload? It seems that looks for new
values, remembering the last state on the ones that actually are commented.
Although it's my fault to have 2 (tow) lines for the same issue, and that I
should realize that this is MY MISTAKE, the log defaults on a reload, if
commented, tend to be the last value entered?

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message G u i d o B a r o s i o 2004-09-01 15:07:39 Re: slower every day
Previous Message Tom Lane 2004-09-01 14:27:05 Re: [NOVICE] Applicationl Crash - Connection reset by peer !!!

Browse pgsql-performance by date

  From Date Subject
Next Message G u i d o B a r o s i o 2004-09-01 15:07:39 Re: slower every day
Previous Message Mr Pink 2004-09-01 12:50:02 Re: Why does a simple query not use an obvious index?