Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f0GEpn093889 for ; Tue, 16 Jan 2001 09:51:49 -0500 (EST) (envelope-from pgsql-interfaces-owner@postgresql.org) Received: from me.tm.ee (adsl895.estpak.ee [213.168.23.133]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0FFks081378; Mon, 15 Jan 2001 10:46:54 -0500 (EST) (envelope-from hannu@tm.ee) Received: from tm.ee (IDENT:hannu@localhost.localdomain [127.0.0.1]) by me.tm.ee (8.9.3/8.9.3) with ESMTP id RAA00918; Mon, 15 Jan 2001 17:42:52 +0200 Message-ID: <3A631A7C.922EAEAC@tm.ee> Date: Mon, 15 Jan 2001 17:42:52 +0200 From: Hannu Krosing X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.17 i686) X-Accept-Language: en MIME-Version: 1.0 To: Alexaki Sofia CC: Tom Lane , pgsql-sql@postgresql.org, pgsql-interfaces@postgresql.org Subject: Re: Re: [SQL] improve performance References: <25588.979572479@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/161 X-Sequence-Number: 775 Tom Lane wrote: > > > 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. And it may even not work, as some system tables (that are also affected by this) may need the full 8k. AFAIK it has never been tested with BLCKSZ < 8k ---------- Hannu