npgsql/Npgsql — pull request #248 by DavidKarlas (2014-05-31 07:58:10+00:00)
Title: [EFMigrations] Always creating setting type text instead of varchar(MaxLength)

I noticed 9.4 is arriving so wanted to check if there is something new with default GUID problem... Same as before...
But while searching on Google I found someone with problem: http://stackoverflow.com/questions/23741521/postgresql-autogeneration-of-uuid-doesnt-work-with-entityframework
So I pulled latest code and wanted to reproduce I ran in different problem...
Same as here: https://groups.google.com/forum/#!topic/npgsql-help/6Szvoq95Of0 I had problem with 1073741823... in EF 6.0.1 if no [MaxLength(#)] was set it was null, then in EF 6.0.2 they changed this to be 1... And now in EF6.1 they are probably looking at https://github.com/npgsql/Npgsql/blob/master/Npgsql.EntityFramework/NpgsqlProviderManifest.Manifest.xml#L22 which has 1073741823

So while looking at what real maximum string length in Pgsql is I ran into this article: http://blog.jonanin.com/2013/11/20/postgresql-char-varchar/

Since EntityFramework is already doing validation of MaxLength value there is no need for setting this things in Postgresql so always setting to TEXT makes sense...