Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0FFS8079441; Mon, 15 Jan 2001 10:28:08 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0FFRxJ25591; Mon, 15 Jan 2001 10:27:59 -0500 (EST) To: Alexaki Sofia cc: pgsql-sql@postgresql.org, pgsql-interfaces@postgresql.org Subject: Re: [SQL] improve performance In-reply-to: References: Comments: In-reply-to Alexaki Sofia message dated "Mon, 15 Jan 2001 15:07:56 +0200" Date: Mon, 15 Jan 2001 10:27:59 -0500 Message-ID: <25588.979572479@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/143 X-Sequence-Number: 757 Alexaki Sofia writes: > Initially I loaded all data in one transaction. Subsequently, I increased > the number of buffers and disabled fsync() (-o -F) and I loaded the > data again but the performance was almost unchanged. Does it make sense?? > How can I improve performance? To note that no indexes are created on the > tables and that I load both "insert into" and "create table" statements. If you can load the data with a COPY command, instead of individual INSERTs, it'll go a lot faster. See also http://www.postgresql.org/devel-corner/docs/postgres/populate.htm > I want to reduce the space (8 Kb) allocated by > DBMS when more space is required to load the data in a table. I reduced > the parameter BLCKSZ but the space allocated remains the same, that is 8 > KB. > How can the allocated space be reduced? If the space was reduced > would loading time and query time increase? I've heard lots of people want to increase BLCKSZ, but you're the first one who ever wanted to reduce it. You sure you want to do this? It's going to make the maximum row length uncomfortably short. Anyway, you probably forgot to do a full rebuild after changing config.h. "make clean" before "make all" is the only way to be sure the configuration change propagates to all the code. Don't forget you will have to do an initdb, also, so back up your data with the old code first. regards, tom lane