Neues vom PostgreSQL Planet

 You are trying to load a CSV file into a database, and almost inevitably, you run into an ERROR: value too long for type character varying 64 if you are using PostgreSQL.  Or SQL Error [1406] [22001]: Data truncation: Data too long for column 'Name' at row 1 if you are using MariaDB or MySQL.

Eight years ago, PostgreSQL introduced scram-sha-256 hashes for passwords.

Eleven months ago, MD5 was deprecated.

Yesterday, I got caught up with all this.

Some of this post will deal with how I fixed it, but mostly it is documenting (for myself) what I did. The fix covers several services and takes place over multiple days.

First, some background on why this change has come into focus for me.

Did you know a table can have no more than 1,600 columns? This blog article was inspired by a conversation Pierre Ducroquet and I had.

First, the documentation

The PostgreSQL documentation Appendix K states a table can have a maximum of 1,600 columns.

After stumbling on a pair of interesting blog posts — You Don’t Need Kafka, Just Use Postgres (Considered Harmful) — somewhat in the style of good old “flame wars” (which are increasingly rare these days) in the recent Postgres Weekly, as a response to a previous article — Kafka is...

 In the previous post, we asked AI to make recommendations to help clean up the data loaded directly from a CSV file. The initial data load for the Name failed because a VARCHAR(64) was estimated to be insufficient to hold the data. But it was not, and a TEXT field was used instead. 

So now we want to save some disk space!  

Starting at $8 USD, the new Developer tier includes everything from the Free tier, with extra disk space, preserved uptime for idle services, and Basic support to keep you building without interruption.