Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mserver5 doesn't detect memory on Solaris/Sparc #2935

monetdb-team opened this issue Nov 30, 2020 · 0 comments

mserver5 doesn't detect memory on Solaris/Sparc #2935

monetdb-team opened this issue Nov 30, 2020 · 0 comments


Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2011-12-06 08:50:08 +0100
From: @grobian
To: MonetDB5 devs <>
Version: 11.5.9 (Aug2011-SP3) [obsolete]
CC: @yzchang

Last updated: 2012-11-27 14:27:41 +0100

Comment 16583

Date: 2011-12-06 08:50:08 +0100
From: @grobian

Aparently, vuurbal has 0.0GiB of memory. In reality, it has 16GiB.

Comment 16600

Date: 2011-12-06 14:16:46 +0100
From: @grobian

The Solaris manpage reportes under the NOTES section:

    Multiplying  sysconf(_SC_PHYS_PAGES)  or  sysconf(_SC_AVPHYS_PAGES)  by
    sysconf(_SC_PAGESIZE)  to  determine  memory amount in bytes can exceed
    the maximum values representable in a 32-bit signed or unsigned  inte‐

Aparently this has changed between the Solaris version on the T1000, since there it reported nicely 4.0GiB available memory. (Out of the 8 it had.)

Comment 16601

Date: 2011-12-06 17:25:55 +0100
From: @grobian

Changeset 312c7c400304 made by Fabian Groffen in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=312c7c400304

Changeset description:

MT_init: avoid overflow for memory on Solaris 32-bits

Fix for bug #2935.  Cap the memorysize to something which can be
addressed in 32-bits, when it happens to be larger than that.  Fixes
memory detection on 32-bits targets for Solaris systems that have lots
of memory installed.

Comment 16823

Date: 2012-01-26 15:32:01 +0100
From: @sjoerdmullender

The Dec2011 version has been release, so declaring this bug as FIXED.

Comment 18081

Date: 2012-11-27 14:27:41 +0100
From: @yzchang

Not possible to add test for this bug, unless someone else knows how...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant