Re: optimizing server for a 10 million row table

General consensus is to use 10-25% of server memory for shared_buffers,
but much of that consensus was generated before 8.0, which introduced a
much more sophisticated management scheme for shared_buffers. Basically,
you need to do some testing to see what setting will work best. Reports
back to here or -performance would be appreciated.

On Sat, Jan 21, 2006 at 12:16:04PM -0600, Tony Caduto wrote:
> Hi,
> we have a client that has a table that holds transactions from sales and
> it is now at 10 million rows. it was in MS Access and they could only
> hold 2 million rows, so we installed Postgres for them and they dumped
> 10 million rows from the mainframe into Postgres.
>
> I was just wondering if anyone had suggestions for optimizing the
> postgresql.conf file and how much OS shared memory I should
> reserve(RedHat is set by default to have 128mb of shared memory).
>
> We are running on RedHat Enterprise Linux 4 AS on a dual processor P4
> Xeon with 2.5 gb of ram.
>
> The table in question has 20 fields and I could post the DDL of the
> table if needed.
>
> Thanks,
>
>
> --
> Tony Caduto
> AM Software Design
> Home of PG Lightning Admin for Postgresql
> http://www.amsoftwaredesign.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461