| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Evandro's mailing lists (Please, don't send personal messages to this address)" <listasjr(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Beyond the 1600 columns limit on windows |
| Date: | 2005-11-08 14:56:28 |
| Message-ID: | 5432.1131461788@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Evandro's mailing lists (Please, don't send personal messages to this address)" <listasjr(at)gmail(dot)com> writes:
> I'm doing a PhD in data mining and I need more than 1600 columns.
I don't think so --- consider redesigning your data model instead.
For instance, maybe you could combine similar columns into an array.
Or split the table into an m:n linking structure. Even coming close
to that implementation limit suggests bad SQL design; if we thought
it was a realistic problem we would have increased it long ago...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-08 15:14:14 | Re: Detect Locked Row Without Blocking |
| Previous Message | Tom Lane | 2005-11-08 14:52:25 | Re: Perl::DBI and interval syntax [side question] |