Re: Specifying the unit in storage parameter

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Specifying the unit in storage parameter
Date: 2014-08-08 03:56:08
Message-ID: 20140808035608.GE7101@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao wrote:
> Hi,
>
> We can specify the unit when setting autovacuum_vacuum_cost_delay
> GUC as follows.
>
> ALTER SYSTEM SET autovacuum_vacuum_cost_delay TO '80ms';
>
> OTOH we cannot specify the unit when setting autovacuum_vacuum_cost_delay
> as storage parameter as follows.
>
> CREATE TABLE test (col1 int) WITH (autovacuum_vacuum_cost_delay = '80ms');
> ERROR: invalid value for integer option
> "autovacuum_vacuum_cost_delay": 80ms
>
> This is not user-friendly.

No disagreement here.

> I'd like to propose the attached patch which
> introduces the infrastructure which allows us to specify the unit when
> setting INTEGER storage parameter like autovacuum_vacuum_cost_delay.
> Comment? Review?

Hm, what's with the parse_int signature change and the hintmsg thing?
Is it just me or the patch is incomplete?

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry White 2014-08-08 04:09:22 Re: jsonb format is pessimal for toast compression
Previous Message Kyotaro HORIGUCHI 2014-08-08 03:40:42 Re: Use unique index for longer pathkeys.