From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Sergey Muraviov <sergey(dot)k(dot)muraviov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: extension_control_path |
Date: | 2014-02-28 10:09:04 |
Message-ID: | m2zjlbft1b.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> # hstore extension
>> comment = 'data type for storing sets of (key, value) pairs'
>> default_version = '1.3'
>> directory = 'local/hstore-new'
>> module_pathname = '$directory/hstore'
>> relocatable = true
>
> Interesting idea. I'm a *little* concerned that re-useing '$directory'
> there might confuse people into thking that any values in the control
> file could be substituted in a similar way though. Would there really
> be much difference between that and '$ctldir' or something?
Well, using $directory makes the feature auto-documented and very easy
to read even without the reference documentation handy. It's also a very
known way to setup things in .ini files.
Now, what other parameters would you possibly use that way, other than
$directory? I can see a use for $default_version, but that's about it.
Would you rather add support for $default_version in the patch, for all
of the parameters just in case, for a different set of control
parameters, or rename the $directory macro?
My vote goes for adding $default_version only.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2014-02-28 10:24:40 | Re: Fwd: patch: make_timestamp function |
Previous Message | Dimitri Fontaine | 2014-02-28 09:59:11 | Re: extension_control_path |