From: | pabloa98 <pabloa98(at)gmail(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: how to add more than 1600 columns in a table? |
Date: | 2019-04-24 22:16:45 |
Message-ID: | CAEjudX5GTFwc1HPn5n1CuZTpYFvYAO61=LxPkUWov9yJFCVVNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
if there is some no-SQL database supporting ACID + generic queries like a
SQL database, I would consider it.
However, the column limit is the problem, no the database. 1200 cols are
reasonable for standard problems. Having a Postgresql supporting thousands
of columns will be useful in Machine Learning and similar domains.
Pablo
On Wed, Apr 24, 2019 at 1:23 PM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> On 4/24/19 3:17 PM, pabloa98 wrote:
> > Hello
> >
> > Sadly today we hit the 1600 columns limit of Postgresql 11.
> >
> > How could we add more columns?
> >
> > Note: Tables are OK. We truly have 2400 columns now. Each column
> > represents a value in a matrix.
> >
> > We have millions of rows so I would prefer not to transpose each row to
> > (x, y, column_value) triplets because it will make all our code more
> > difficult of what it is.
> >
> > Any help, very appreciated.
>
> Is a relational database the proper tool for the job?
>
> --
> Angular momentum makes the world go 'round.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2019-04-24 22:27:56 | Re: how to add more than 1600 columns in a table? |
Previous Message | pabloa98 | 2019-04-24 22:14:13 | Re: how to add more than 1600 columns in a table? |