Re: More then 1600 columns? - Mailing list pgsql-general

From Clark C. Evans
Subject Re: More then 1600 columns?
Date
Msg-id 1289597138.17195.1405027223@webmail.messagingengine.com
Whole thread Raw
In response to Re: More then 1600 columns?  (Dann Corbit <DCorbit@connx.com>)
Responses Re: More then 1600 columns?  (Dmitriy Igrishin <dmitigr@gmail.com>)
Re: More then 1600 columns?  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-general
On Fri, 12 Nov 2010 21:10 +0000, "Dann Corbit" wrote:
> If (for access) the single table seems simpler, then
> a view can be used.

Even if you "partition" the columns in the instrument
over N tables, you still can't query it in a single
result set.   The limit is quite deep in PostgreSQL
and extends to tuples, including views and in-memory
query results.

I find that partitioning does work, but it requires extra
care on the part of the application developer that really
shouldn't be necessary.

Best,

Clark

pgsql-general by date:

Previous
From: Dann Corbit
Date:
Subject: Re: More then 1600 columns?
Next
From: Dmitriy Igrishin
Date:
Subject: Re: More then 1600 columns?