From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Mark Mitchell" <mmitchell(at)riccagroup(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: More then 1600 columns? |
Date: | 2010-11-12 16:08:40 |
Message-ID: | 11011.1289578120@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Mark Mitchell" <mmitchell(at)riccagroup(dot)com> writes:
> 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 own field. I had lots of comments on why I should not do this and the possible alternatives and I thank everyone for their input but no one answered the question about compiling with a higher block size to get more columns. Can anyone answer that?
Yes, I did answer it: there is no such compilation option.
If you were willing to run a very nonstandard version of Postgres, you
could try widening t_hoff (see src/include/access/htup.h) but there is
nobody who can tell you what the fallout from that might be. One big
concern that I would have is the likelihood of O(N^2) behavior on very
long query targetlists.
On the whole I think you'd be a lot better off looking into hstore,
especially the improved 9.0 version.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Mitchell | 2010-11-12 16:25:43 | Re: More then 1600 columns? |
Previous Message | Sachin Srivastava | 2010-11-12 16:03:30 | Re: Help with Stack Builder |