Re: effective_cache_size cannot be changed by a reload

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: effective_cache_size cannot be changed by a reload
Date: 2014-03-20 12:03:46
Message-ID: CAHGQGwGgFq+2NSjsq=XE+9MhOOeT6+u95OhqZ0sCt0vq_D1CHA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 20, 2014 at 2:34 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> In 9.4dev, if the server is started with effective_cache_size = -1, then it
> cannot be changed away from that without a restart. If you change the
> config file and do a reload or pg_reload_conf(), it ignores the change
> without comment in the logs.
>
> If you start the server with a value other than -1, then you can change the
> value by editing the file and doing a reload. You can even change it to -1,
> and then change it back away from -1 again.

I think that's a bug. Patch attached.

> I don't know if bugs reports (without patches) against pre-release versions
> are supposed to go to hackers or to bugs.

Either works at least for me.

Regards,

--
Fujii Masao

Attachment Content-Type Size
bugfix.patch text/x-diff 645 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2014-03-20 12:32:18 Re: jsonb and nested hstore
Previous Message Petr Jelinek 2014-03-20 11:39:38 Re: Review: plpgsql.extra_warnings, plpgsql.extra_errors