From: | John Klos <john(at)ziaspace(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dave McGuire <mcguire(at)neurotica(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, port-vax(at)netbsd(dot)org, vax(at)openbsd(dot)org, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL for VAX on NetBSD/OpenBSD |
Date: | 2014-06-29 19:39:29 |
Message-ID: | Pine.NEB.4.64.1406291937080.875@andromeda.ziaspace.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Well, the issue from our point of view is that a lot of what we care about
> testing is extremely low-level hardware behavior, like whether spinlocks
> work as expected across processors. It's not clear that a simulator would
> provide a sufficiently accurate emulation.
>
> OTOH, the really nasty issues like cache coherency rules don't arise in
> single-processor systems. So unless you have a multiprocessor VAX
> available to spin up, a simulator may tell us as much as we'd learn
> anyway.
>
> (If you have got one, maybe some cash could be found --- we do have
> project funds available, and I think they'd be well spent on testing
> purposes. I don't make those decisions though.)
Depending on how often you'd like the system to try to run a compile, I'd
be happy to run it on a VAXstation 4000/60. It runs bulk package builds
for pkgsrc, but we could do a compile every week or so (every day would
really eat into cycles for other packages).
John
From | Date | Subject | |
---|---|---|---|
Next Message | Johnny Billquist | 2014-06-29 19:41:27 | Re: PostgreSQL for VAX on NetBSD/OpenBSD |
Previous Message | Tom Lane | 2014-06-29 19:35:07 | Re: PostgreSQL for VAX on NetBSD/OpenBSD |