From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Yuri Levinsky <yuril(at)celltick(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: requested shared memory size overflows size_t |
Date: | 2014-03-14 02:41:26 |
Message-ID: | 53226C56.6000101@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/04/2014 10:53 PM, Yuri Levinsky wrote:
> Please advise me: I just downloaded the source and compiled it. Sun Spark Solaris 9 is always 64 bit, I verified it with sys admin. He may run 32 bit applications as well. Have I use some special option during compilation to verify that compiled PostgreSQL is actually 64 bit app?
Many platforms include both 32-bit and 64-bit target toolchains. So you
might be on a 64-bit platform, but that doesn't mean you aren't
compiling a 32-bit executable.
Please run:
grep '^#define SIZEOF' config.log
and post the results.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2014-03-14 03:42:23 | Re: issue log message to suggest VACUUM FULL if a table is nearly empty |
Previous Message | Josh Berkus | 2014-03-14 01:07:38 | Re: Replication slots and footguns |