Yes I understand that this is "bad design" but what we are doing is storing each form field in a survey in its own
column.For very long surveys we end up with thousands of elements.
I know storing in an array is possible but it makes it so much easier to query the data set when each element is in its
ownfield. I had lots of comments on why I should not do this and the possible alternatives and I thank everyone for
theirinput but no one answered the question about compiling with a higher block size to get more columns. Can anyone
answerthat?
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, November 12, 2010 12:24 AM
To: Mark Mitchell
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] More then 1600 columns?
"Mark Mitchell" <mmitchell@riccagroup.com> writes:
> Is there are hard limit of 1600 that you cannot get around?
Yes.
Generally, wanting more than a few dozen columns is a good sign that you
need to rethink your schema design. What are you trying to accomplish
exactly?
regards, tom lane
