Re: requested shared memory size overflows size_t

Поиск
Список
Период
Сортировка
От Yuri Levinsky
Тема Re: requested shared memory size overflows size_t
Дата
Msg-id C9278837BA426D4DBDF8996DB890232612AA4E@Cobra.celltick.com
обсуждение исходный текст
Ответ на Re: requested shared memory size overflows size_t  (Craig Ringer <craig@2ndquadrant.com>)
Ответы Re: requested shared memory size overflows size_t  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-hackers
Dear Craig,
The output is:
#define SIZEOF_OFF_T 8
#define SIZEOF_VOID_P 4
#define SIZEOF_SIZE_T 4
#define SIZEOF_LONG 4

Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable-shared
--enable-languages=c,c++,f77
Thread model: posix
gcc version 3.4.6



Sincerely yours,


Yuri Levinsky, DBA
Celltick Technologies Ltd., 32 Maskit St., Herzliya 46733, Israel
Mobile: +972 54 6107703, Office: +972 9 9710239; Fax: +972 9 9710222

-----Original Message-----
From: Craig Ringer [mailto:craig@2ndquadrant.com] /define
Sent: Friday, March 14, 2014 4:41 AM
To: Yuri Levinsky; Robert Haas
Cc: Heikki Linnakangas; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] requested shared memory size overflows size_t

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
withsys admin. He may run 32 bit applications as well. Have I use some special option during compilation to verify that
compiledPostgreSQL 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
meanyou 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Upcoming back branch releases
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: [RFC] What should we do for reliable WAL archiving?