Re: [GENERAL] optimizing advice

2009-12-01 Thread Bret
> -Original Message- > From: pgsql-general-ow...@postgresql.org > [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Scott Marlowe > Sent: Tuesday, December 01, 2009 2:10 PM > To: r.soeren...@mpic.de > Cc: pgsql-general@postgresql.org > Subject: Re: [GENER

Re: [GENERAL] optimizing advice

2009-12-01 Thread Scott Marlowe
2009/12/1 Rüdiger Sörensen : > dear all, > > I am building a database that will be really huge and grow rapidly. It holds > data from satellite observations. Data is imported via a java application. > The import is organized via files, that are parsed by the application; each > file hods the data o

Re: [GENERAL] optimizing advice

2009-12-01 Thread Edgardo Portal
On 2009-12-01, Rüdiger Sörensen wrote: > dear all, > > I am building a database that will be really huge and grow rapidly. It > holds data from satellite observations. Data is imported via a java > application. The import is organized via files, that are parsed by the > application; each file h

Re: [GENERAL] optimizing advice

2009-12-01 Thread Vick Khera
On Tue, Dec 1, 2009 at 2:58 PM, Steve Atkins wrote: > For the bulk imports of old data, import the data first, then build the > indexes and add constraints later. Disable autovacuum during the initial bulk > import. Also, consider turning fsync off for those imports (less of a win on > modern v

Re: [GENERAL] optimizing advice

2009-12-01 Thread Steve Atkins
On Dec 1, 2009, at 1:34 AM, Rüdiger Sörensen wrote: > dear all, > > I am building a database that will be really huge and grow rapidly. It holds > data from satellite observations. Data is imported via a java application. > The import is organized via files, that are parsed by the application;