In the discussion we found the following compromise: The postinst should
ignore the locale from the environment (as sudo and ssh make that
unreliable), and instead do the following fallback:
* if /etc/default/locale defines a locale, use that
* otherwise, if /etc/environment defines a locale, use that (that's a pam_env
file, so source that in a subprocess and handle errors!)
* otherwise, use C
That will break cases where the system locale is defined someplace else,
but then people can still either drop and re-create the default cluster,
or specify the locale on creating new DBs.
** Package changed: postgresql-9.1 (Ubuntu) => postgresql-common (Ubuntu)
** Changed in: postgresql-common (Ubuntu)
Importance: Undecided => Low
** Changed in: postgresql-common (Ubuntu)
Status: Invalid => In Progress
** Changed in: postgresql-common (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969462
Title:
fails to start after install if invalid locale is set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/969462/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
