Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 771981C6FE3C for ; Thu, 26 Jan 2012 11:39:38 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RqRQE-0003vR-87 for pgsql-admin@postgresql.org; Thu, 26 Jan 2012 15:39:38 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q0QFdLL9004664; Thu, 26 Jan 2012 10:39:21 -0500 (EST) To: Yannick Monclin cc: pgsql-admin@postgresql.org Subject: Re: extend column limit with blocksize does not work In-reply-to: <4F2147DC.1010002@univ-reims.fr> References: <4F2147DC.1010002@univ-reims.fr> Comments: In-reply-to Yannick Monclin message dated "Thu, 26 Jan 2012 13:32:28 +0100" Date: Thu, 26 Jan 2012 10:39:21 -0500 Message-ID: <4663.1327592361@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201201/145 X-Sequence-Number: 39057 Yannick Monclin writes: > I use the query survey software "Limesurvey", when this sofware build > some complex survey, it's necessary to have more than 1600 columns in > one table. I'd suggest rethinking the database schema. Even if you could get that to work, it's likely to perform pretty horridly. > So, i have used this parameter (configure > --with-blocksize=32) to build my last postgresql (9.1.2). BLCKSZ is not the limiting factor here --- it's the tuple header format, specifically the width of t_hoff. You might care to look at the first few comments in src/include/access/htup.h. regards, tom lane