Bug #20937
closed
Postgresql is not created with the UTF8 encoding
Added by Nicolas CHARLES over 2 years ago.
Updated over 1 year ago.
Category:
System integration
Description
It uses the system one, and well, sometimes we don't want that
CREATE DATABASE "rudder" WITH OWNER = "rudder" encoding = "UTF8"
should do the trick
- Target version changed from 6.2.13 to 6.2.14
- Target version changed from 6.2.14 to 6.2.15
- Target version changed from 6.2.15 to 6.2.16
- Target version changed from 6.2.16 to 6.2.17
- Target version changed from 6.2.17 to 997
- Target version changed from 997 to 6.2.18
- Target version changed from 6.2.18 to 6.2.19
- Target version changed from 6.2.19 to 6.2.20
- Target version changed from 6.2.20 to old 6.2 issues to relocate
- Target version changed from old 6.2 issues to relocate to 7.2.7
- Regression set to No
- Status changed from New to In progress
- Assignee changed from Nicolas CHARLES to François ARMAND
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2729
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.7 and 7.3.2 which were released today.
- Related to Bug #23388: Server install fails with postgresql encoding error added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous