sql - Are there downsides for creating a large VARCHAR value in Redshift? -


the source data keeps throwing values field keep on getting bigger , bigger in length. right i'm using varchar(200) might go varchar(400). there disadvantages using large number?

what mean "downside"? there big downside if don't make column big enough -- can't use store values want store there.

as additional overhead, don't need worry that. varchar() type takes storage needed value, plus small overhead length. also, "400" not such big number, when compared "200".

so, if need 400 bytes store value, change table store it. there may overhead changing length of value. i'm not sure if redshift feel need copy data because type changed. however, effect on performance should negligible.


Comments

Popular posts from this blog

c++ - Difference between pre and post decrement in recursive function argument -

php - Nothing but 'run(); ' when browsing to my local project, how do I fix this? -

php - How can I echo out this array? -