Thread: maintenance_work_mem upper limit =1gb??
why has been maintenance_work_mem and work_mem been
restricted to 1gb... although i dont need it but kinda
server i am working on.... i wont mind
allocating...(32gb ram)....
#define MaxAllocSize ((Size) 0x3fffffff)
/* 1 gigabyte - 1 */
also for those who dont know the max. shared_buffer=
262143 (= 2^31 (INT_MAX) / 8192(size of each
buffer)...) comes to be around 2Gb...
although i would like to set this high also... but the
reasoning for its limit seems logical...
developers might want to increase these limits.. with
the kind-of 64 bits available now... might speed up
the things little bit ;)
Regards
Himanshu
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/
Himanshu Baweja <himanshubaweja@yahoo.com> writes:
> why has been maintenance_work_mem and work_mem been
> restricted to 1gb...
So as not to overflow on 32-bit machines.
regards, tom lane
Tom Lane writes:
>Himanshu Baweja writes:
>> why has been maintenance_work_mem and work_mem been
>> restricted to 1gb...
>> why has been maintenance_work_mem and work_mem been
>> restricted to 1gb...
>So as not to overflow on 32-bit machines.
then why not add a check during configure(before compiling) to check if its a 32 or 64 bit machine.... in the past we have seen servers like DEC and Sun... which although 32 bit used to support much more memory.... although i can just give suggestion... its upto u to see whts good and whts not...
by the way i have started to like postgres.. it really roks... thx to all the developers :)
Regards
Himanshu
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com