Re: buildfarm vs code

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: buildfarm vs code
Date: 2018-06-06 17:52:13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)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
> '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.

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.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2018-06-06 18:04:09 Re: POC: GROUP BY optimization
Previous Message Jeremy Schneider 2018-06-06 17:39:36 Re: Code of Conduct plan