The day I reached the 1600 columns limit in PostgreSQL
rosenfeld.herokuapp.com
The day I reached the 1600 columns limit in PostgreSQL
1–10 of 16 posts
Re: The day I reached the 1600 columns limit in PostgreSQL
#2Maybe Im missing the point, but After reading that I still don't understand why you couldn't just add a permanent column and continually overwrite it.
Re: The day I reached the 1600 columns limit in PostgreSQL
#3Why Is there a limit on the number of columns I can have, and if something bad happens from having too many, why isn't the limit much lower than 1600, which hopefully most of us can agree is already way beyond absurd?
Re: The day I reached the 1600 columns limit in PostgreSQL
#4Maybe Im missing the point, but After reading that I still don't understand why you couldn't just add a permanent column and continually overwrite it.
You don't understand it because he doesn't understand the problem well enough to explain it, which is why he ever had this problem in the first place.
Re: The day I reached the 1600 columns limit in PostgreSQL
#5Maybe Im missing the point, but After reading that I still don't understand why you couldn't just add a permanent column and continually overwrite it.
You don't understand it because he doesn't understand the problem well enough to explain it, which is why he ever had this problem in the first place.
My thoughts exactly.
Re: The day I reached the 1600 columns limit in PostgreSQL
#6Maybe Im missing the point, but After reading that I still don't understand why you couldn't just add a permanent column and continually overwrite it.
You don't understand it because he doesn't understand the problem well enough to explain it, which is why he ever had this problem in the first place.
Any chance we can get a quick post mortem?
Re: The day I reached the 1600 columns limit in PostgreSQL
#7Why Is there a limit on the number of columns I can have, and if something bad happens from having too many, why isn't the limit much lower than 1600, which hopefully most of us can agree is already way beyond absurd?
It has to do with how the tuple header that stores the metadata is designed. See comments here: https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f...
Re: The day I reached the 1600 columns limit in PostgreSQL
#8Maybe Im missing the point, but After reading that I still don't understand why you couldn't just add a permanent column and continually overwrite it.
Yeah, reading the old id and then using the new id seems like the textbook example of db triggers.
Re: The day I reached the 1600 columns limit in PostgreSQL
#9Earlier quoted context omitted.
You don't understand it because he doesn't understand the problem well enough to explain it, which is why he ever had this problem in the first place.
Any chance we can get a quick post mortem?
He used a temp table to stash IDs, like he should have from the start.
Re: The day I reached the 1600 columns limit in PostgreSQL
#10I had this problem for real and there was no solution: parsing Edgar sec quarterly reports and trying to stick every field into its column. there was no solution so we just through out some of the fields.