From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | NBoardman(at)idtus(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13853: initdb to UNC path |
Date: | 2016-01-07 18:49:19 |
Message-ID: | 568EB32F.7060001@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 1/7/2016 8:14 AM, NBoardman(at)idtus(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13853
> Logged by: Nuri Boardman
> Email address:NBoardman(at)idtus(dot)com
> PostgreSQL version: 9.4.2
> Operating system: Windows 7
> Description:
>
> when i run this command (initdb with UNC path)
> pg_ctl initdb -D \\localhost\Users\nboardman\test
>
> i get the following (error) output
>
> The files belonging to this database system will be owned by user
> "NBoardman".
> This user must also own the server process.
>
> The database cluster will be initialized with locale "English_United
> States.1252
> ".
> The default database encoding has accordingly been set to "WIN1252".
> The default text search configuration will be set to "english".
>
> Data page checksums are disabled.
>
> fixing permissions on existing directory //localhost/Users/nboardman/test
> ... ok
>
> creating subdirectories ... initdb: could not create directory
> "//localhost/Users": File exists
> initdb: removing contents of data directory
> "//localhost/Users/nboardman/test"
> pg_ctl: database system initialization failed
>
> finally, if this is illegal, the documentation does not indicate the path
> has to be a windows path
> fromhttp://www.postgresql.org/docs/9.4/static/app-initdb.html
does it work if you leave out the \\localhost part? using network
paths for database storage is NOT recommended.
the documentation is OS independent, things like 'paths' are OS specific
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-01-07 19:20:58 | Re: BUG #13853: initdb to UNC path |
Previous Message | Tom Lane | 2016-01-07 18:40:28 | Re: BUG #13848: 2016 Week Number Error |