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 l
Well, the fact that initdb didn't produce a working configuration and
that make installcheck failed to work properly are bad. But, yeah,
it's not totally broken.
I think it did create a working configuration (with the exception of
postgresql.conf), because I can run psql and do stuff on the co
That's all I have time for tonight. Is there an easier way to run a
testsuite?
I think you're doing it right, but apparently configure is
mis-identifying which flags are needed for thread-safety on your
platform. It's possible configuring with --disable-thread-safety
would help, or you could ma
Hi,
What value did it select for shared_buffers? How much memory does a
high-end VAX have? These days, we try to set shared_buffers = 128MB
if the platform will support it, but it's supposed to fall back to
smaller values if that doesn't work. It will try allocating that much
though, at least
Hi,
Has anyone tried to build PostgreSQL for VAX lately? If so, did it
compile? Did you have to use --disable-spinlocks to get it to compile?
If it did compile, can you actually run it, and does it pass the
regression tests and work as expected? Would you be willing to work
with the Postgr
