Heikki Linnakangas wrote: > If we go with that, we should probably make the notion of a default > collation explicit. We could set pg_database.datcollate/datctype column > to NULL to mean "use the cluster default".
I'm not sure how this would work. If I initdb with a certain locale/encoding and then create a database with default locale/encoding, how would a restore work on a cluster that has been initdb'd with a different locale/encoding? If you don't dump the locale specification, it could very well not match what the user intended. > I don't find the idea of creating mapping tables of locale names very > appetizing. Looking at our encoding name mapping table, there's quite a > few different spellings of different encoding names alone, let alone all > locale names. Yeah, it doesn't seem pleasant that way. When I proposed it I was thinking that the mapping would be specified by the user. OTOH since it's only pg_dumpall output that's the problem, this idea is not be very useful because there will be no way for a tool to do the replacement. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
