From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Refactoring GUC unit conversions |
Date: | 2015-02-13 17:44:35 |
Message-ID: | 54DE3803.1010209@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2015-02-13 18:01:22 | Re: pg_basebackup may fail to send feedbacks. |
Previous Message | Heikki Linnakangas | 2015-02-13 17:43:14 | Re: Redesigning checkpoint_segments |