matthew green <[EMAIL PROTECTED]> writes:
> i also believe the `Bad address' errors were caused when the test
> was run in an NFS mounted directory.
You may have something, there. My test run on the VAX was over NFS.
I set up NetBSD on a VAX specifically to test PostgreSQL 7.1, but I
didn't hav
> >> CREATE INDEX hash_i4_index ON hash_i4_heap USING hash (random int4_ops);
> >> + ERROR: cannot read block 3 of hash_i4_index: Bad address
>
> "Bad address"? That seems pretty bizarre.
This is obviously something that shows up on _some_ NetBSD platforms.
The above w
matthew green <[EMAIL PROTECTED]> writes:
> digging into the regression.diffs, i can see that:
> - reltime failed because it just had:
> ! psql: Backend startup failed
>The postmaster log file should have more info, but a first thought is
>that you ran up against
>> digging into the regression.diffs, i can see that:
>> - reltime failed because it just had:
>> ! psql: Backend startup failed
The postmaster log file should have more info, but a first thought is
that you ran up against process or swap-space limitations. The parallel
>> i will be reinstalling this SS20 with a full installation sometime in
>> the next few days. i will re-run the testsuite after this to see if
>> that is causing any of the lossage.
Please let us know.
actually, i had a classic i could test with -- all except horology passe
> after running `unlimit' (tcsh) before `make check', the only failures i have
> are the horology (expected) and the inherit sorted failures, on NetBSD/sparc64.
I'll mark both NetBSD/sparc as supported, for both 32 and 64-bit builds.
Thanks!
- Thomas
Tom Ivar Helbekkmo <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
> CREATE INDEX hash_i4_index ON hash_i4_heap USING hash (random int4_ops);
> + ERROR: cannot read block 3 of hash_i4_index: Bad address
>>
>> "Bad address"? That seems pretty bizarre.
> This is obviously some
matthew green <[EMAIL PROTECTED]> writes:
> digging into the regression.diffs, i can see that:
> - reltime failed because it just had:
> ! psql: Backend startup failed
>The postmaster log file should have more info, but a first thought is
>that you ran up against process or swap-space
Tom Lane <[EMAIL PROTECTED]> writes:
> >> CREATE INDEX hash_i4_index ON hash_i4_heap USING hash (random int4_ops);
> >> + ERROR: cannot read block 3 of hash_i4_index: Bad address
>
> "Bad address"? That seems pretty bizarre.
This is obviously something that shows up on _some_ NetBSD platforms
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Anyone have suggestions for Mathew?
>> for postgresql-7.1RC2.tar.gz, here is my `make check' for NetBSD/sparc64:
>> digging into the regression.diffs, i can see that:
>> - reltime failed because it just had:
>> ! psql: Backend startup failed
The pos
(cc'd the -hackers mailing list)
Thanks for the reports Matthew. There is a single failure in the
NetBSD/sparc64 test due to a problem in the reltime test (or in starting
the reltime test). There is a different failure in your NetBSD/sparc
test, but since you are not confident about your installa
11 matches
Mail list logo
