| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Isolation checks under MSVC |
| Date: | 2011-05-23 12:56:18 |
| Message-ID: | 4DDA5972.5080605@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/16/2011 04:09 AM, Magnus Hagander wrote:
> On Mon, May 16, 2011 at 06:14, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>> I've committed a bunch of changes both in the Postgres code and the
>> buildfarm code to enable running the isolation checks under MSVC. There's
>> one hurdle that I haven't overcome: the code tries to call
>> "./isolationtester" and Windows barfs on it. I think we need to remove that
>> way of doing things, and instead user a full path for such commands like we
>> do elsewhere.
> That seems like the reasonable way to fix it, yes.
It turns out that the real problem was that I'd put a spurious
underscore in the name of the .exe in the MSVC build. That's been fixed
now and this is all working.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2011-05-23 13:32:55 | Re: SSI predicate locking on heap -- tuple or row? |
| Previous Message | Bruce Momjian | 2011-05-23 12:26:27 | Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. |