Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B67F7475F32; Thu, 23 Jan 2003 12:58:38 -0500 (EST) Received: from localhost.localdomain (unknown [194.204.44.121]) by postgresql.org (Postfix) with ESMTP id 43EA247651B; Thu, 23 Jan 2003 12:42:35 -0500 (EST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.5/8.12.5) with ESMTP id h0NHgULV001458; Thu, 23 Jan 2003 19:42:31 +0200 Received: (from hannu@localhost) by localhost.localdomain (8.12.5/8.12.5/Submit) id h0NHgQli001456; Thu, 23 Jan 2003 19:42:26 +0200 X-Authentication-Warning: localhost.localdomain: hannu set sender to hannu@tm.ee using -f Subject: Re: Terrible performance on wide selects From: Hannu Krosing To: Dann Corbit Cc: Tom Lane , Steve Crawford , pgsql-performance@postgreSQL.org, pgsql-hackers@postgreSQL.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1043343746.1368.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 23 Jan 2003 19:42:26 +0200 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/895 X-Sequence-Number: 34505 Dann Corbit kirjutas N, 23.01.2003 kell 02:22: > [snip] > > So (for instance) if you have 12 variable fields, you would > > store 12 integers at the start of the record. > > Additionally, you could implicitly size the integers from the properties > of the column. A varchar(255) would only need an unsigned char to store > the offset, but a varchar(80000) would require an unsigned int. I guess that the pointer could always be 16-bit, as the offset inside a tuple will never be more (other issues constrain max page size to 32K) varchar(80000) will use TOAST (another file) anyway, but this will be hidden inside the field storage in the page) > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster -- Hannu Krosing