Re: Refactoring GUC unit conversions - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Refactoring GUC unit conversions
Date
Msg-id 54DE3803.1010209@vmware.com
Whole thread Raw
In response to Re: Refactoring GUC unit conversions  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Refactoring GUC unit conversions  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 02/13/2015 07:34 PM, Jim Nasby wrote:
> On 2/13/15 7:26 AM, Heikki Linnakangas wrote:
>> In the "redesign checkpoint_segments" patch, Robert suggested keeping
>> the settings' base unit as "number of segments", but allow conversions
>> from MB, GB etc. I started looking into that and found that adding a new
>> unit to guc.c is quite messy. The conversions are done with complicated
>> if-switch-case constructs.
>>
>> Attached is a patch to refactor that, making the conversions
>> table-driven. This doesn't change functionality, it just makes the code
>> nicer.
>
> Looks good, but shouldn't there be a check for a unit that's neither
> memory or time?

Can you elaborate? We currently only support units for memory and time 
settings.

- Heikki




pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Redesigning checkpoint_segments
Next
From: Fujii Masao
Date:
Subject: Re: pg_basebackup may fail to send feedbacks.