Re: cannot to set track_activity_query_size in kB

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: cannot to set track_activity_query_size in kB
Date: 2014-04-09 14:03:35
Message-ID: CAFj8pRBvb-kJ7BsdzLAvpuHt1ZL-qBHw2Hh6cCv6kT=ZemWr_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2014-04-09 12:54 GMT+02:00 Bruce Momjian <bruce(at)momjian(dot)us>:

> On Wed, Apr 9, 2014 at 11:25:23AM +0200, Pavel Stehule wrote:
> > Hello
> >
> > I got a message
> >
> > LOG: invalid value for parameter "track_activity_query_size": "64kB"
> > FATAL: configuration file "/usr/local/pgsql/data/postgresql.conf"
> contains
> > errors
> >
> > for
> >
> > track_activity_query_size = 64kB
>
> I looked into this and the cause is that we don't have any _bytes_ GUC
> unit setting, we only have 3:
>
> #define GUC_UNIT_KB 0x0400 /* value is in kilobytes */
> #define GUC_UNIT_BLOCKS 0x0800 /* value is in blocks */
> #define GUC_UNIT_XBLOCKS 0x0C00 /* value is in xlog blocks
> */
> #define GUC_UNIT_MEMORY 0x0C00 /* mask for KB, BLOCKS,
> XBLOCKS */
>
> Should I add a _bytes_ setting so this works, or just add a C comment
> that it doesn't?
>

Change this value is not usual, so it can be only in KB - but, can be nice
it be commented there

Regards

Pavel

>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + Everyone has their own god. +
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2014-04-10 01:52:18 Re: BUG #8695: Reloading dump fails at COMMENT ON EXTENSION plpgsql
Previous Message Tom Lane 2014-04-09 14:00:17 Re: cannot to set track_activity_query_size in kB