Re: Physical sites handling large data - Mailing list pgsql-general

From Tom Lane
Subject Re: Physical sites handling large data
Date
Msg-id 28735.1032102076@sss.pgh.pa.us
Whole thread Raw
In response to Re: Physical sites handling large data  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
Responses Re: Physical sites handling large data
List pgsql-general
"Shridhar Daithankar" <shridhar_daithankar@persistent.co.in> writes:
> On this topic, say I decide to devote 8GB to postgres that means 1048576
> buffers for 8K page size. Need I push available number of shared memory
> segments beyond this value? Can I tweak size of page? If I can would it help
> for such an installation?

I do not believe you can push the shared memory size past 2GB, or about
250K buffers, because the size calculations for it are done in "int"
arithmetic.  Of course, this could be fixed if anyone cared to do the
legwork.  I doubt there's much point in worrying about it though.
A larger memory is still usable, it's just that the rest of it will be
used in the form of kernel-level disk cache not Postgres buffers.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: bigint datatype accepting floating numbers
Next
From: Shridhar Daithankar
Date:
Subject: Re: user defined data types - help