Re: extension_control_path

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Sergey Muraviov <sergey(dot)k(dot)muraviov(at)gmail(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: extension_control_path
Date: 2014-01-25 09:15:20
Message-ID: CABUevEyr9KA_4BZG=H8x__2PmA8eK_swxUjV3YjjJ44E0hgyaA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)k(dot)muraviov(at)gmail(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2014-01-25 09:42:49 Re: proposal: hide application_name from other users
Previous Message David Rowley 2014-01-25 08:50:06 Re: [PATCH] Negative Transition Aggregate Functions (WIP)