Re: extension_control_path - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: extension_control_path
Date
Msg-id CABUevEyr9KA_4BZG=H8x__2PmA8eK_swxUjV3YjjJ44E0hgyaA@mail.gmail.com
Whole thread Raw
In response to Re: extension_control_path  (Sergey Muraviov <sergey.k.muraviov@gmail.com>)
Responses Re: extension_control_path  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: extension_control_path  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
I haven't actually looked at the patch itself, but I noted this from the other review:


On Fri, Jan 24, 2014 at 6:43 PM, Sergey Muraviov <sergey.k.muraviov@gmail.com> wrote:
=================================================

postgresql.conf:
   extension_control_path = '/extensions/postgis-2.0.4:/extensions/postgis-2.1.1'


Using colon as the path separator is going to break on windows. The patch notices this and uses semicolon on Windows instead. Do we really want to go down that path - that means that everybody who writes any sorts of installation instructions including this will have to make them separate for different platforms. Shouldn't we just use semicolon on all platforms, for consistency?


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [PATCH] Negative Transition Aggregate Functions (WIP)
Next
From: Greg Stark
Date:
Subject: Re: proposal: hide application_name from other users