On Fri, Oct 2, 2015 at 5:21 PM, John Gunter <john.gunter@weather.com> wrote:
> I don't dispute your claim that they should design their product to work
> with yours...
>
> But this registry value DID change between 9.3.5.3 and 9.3.9.3
>
> In 9.3.5.3 it's
> C:\Program Files (x86)\Postgresql\9.3
>
> in 9.3.9.3 it's
> C:/Program Files (x86)/Postgresql/9.3
Hmm, my apologies - you're right. I think what I was remembering was
that the value *could* previously have forward slashes, if the path
was passed in that way on the command line.
Anyway - Sandeep; can you explain this change?
> I will attempt to make this change apparent to PostGIS. Perhaps they can
> update their installer and give me one that will work with this change.
>
> Thank you!
>
> On Fri, Oct 2, 2015 at 12:00 PM, Dave Page <dpage@pgadmin.org> wrote:
>>
>> On Fri, Oct 2, 2015 at 3:22 PM, <jgunter@wsi.com> wrote:
>> > The following bug has been logged on the website:
>> >
>> > Bug reference: 13662
>> > Logged by: John Gunter
>> > Email address: jgunter@wsi.com
>> > PostgreSQL version: 9.3.9
>> > Operating system: Windows
>> > Description:
>> >
>> > In the "Base Directory" registry entry the Slashes are FORWARD.
>> >
>> > The PostGIS installer uses this value to populate the install directory
>> > and
>> > PostGIS will NOT install with this path
>> >
>> > C:/Program Files (x86)/Postgresql/9.3
>>
>> PostGIS' installer is designed to work with ours, not the other way
>> round. The PG installer has been this way since it was first released,
>> so arguably this is their bug.
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
