On 06/06/2018 01:52 PM, Tom Lane wrote:
Andrew Dunstan <andrew.duns...@2ndquadrant.com> writes:
On 06/06/2018 10:24 AM, Tom Lane wrote:
I'm curious to know what the failure looks like exactly?
[00:07:37] 2018-06-06 17:25:41.662 UTC [1904:7] pg_regress/tablespace
ERROR: could not set permissions on directory
"C:/projects/pg-devel/src/test/regress/testtablespace": Permission denied
[00:07:37] 2018-06-06 17:25:41.662 UTC [1904:8] pg_regress/tablespace
STATEMENT: CREATE TABLESPACE regress_tblspace LOCATION
'C:/projects/pg-devel/src/test/regress/testtablespace';
Hmph. So, looking at tablespace.c, what we're seeing is chmod() returning
EACCES. AFAICT from googling, Microsoft do provide chmod() directly, it's
not some emulation of ours ... but they don't document that an EACCES
failure is even possible, let alone what the triggering conditions are.
Sigh.
Perhaps it'd be useful for investigation purposes to replace the chmod()
with whatever the native Windows equivalent is, and see just which
Microsoft error code it returns.
Maybe this should be SetSecurityInfo().
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
