From: Tom Lane <tgl@sss.pgh.pa.us>
To: Yannick Monclin <yannick.monclin@univ-reims.fr>
Cc: pgsql-admin@postgresql.org
Subject: Re: extend column limit with blocksize does not work
Date: Thu, 26 Jan 2012 10:39:21 -0500
Message-ID: <4663.1327592361@sss.pgh.pa.us> (raw)
In-Reply-To: <4F2147DC.1010002@univ-reims.fr>
References: <4F2147DC.1010002@univ-reims.fr>
Yannick Monclin <yannick.monclin@univ-reims.fr> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, yannick.monclin@univ-reims.fr
Subject: Re: extend column limit with blocksize does not work
In-Reply-To: <4663.1327592361@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox