Remark : I can't alter the database as suggested in this solution : ALTER DATABASE database_name SET datestyle TO "ISO, YDM" īecause that format YDM isn't conform with the postgresql datestyle.Īccording to the postgresql documentation LC_COLLATE and LC_TYPE can not be modified once a database is created, but that's not problematic since it's possible to recreate the database once those two variables are properly set. Lc_time = 'fr_FR.UTF-8' # locale for time formattingĭefault_text_search_config = 'pg_catalog.english' Lc_numeric = 'fr_FR.UTF-8' # locale for number formatting Lc_monetary = 'fr_FR.UTF-8' # locale for monetary formatting Lc_messages = 'en_US.UTF-8' # locale for system error message # These settings are initialized by initdb, but they can be changed. #client_encoding = sql_ascii # actually, defaults to database #timezone_abbreviations = 'Default' # Select the set of available time zone That's the pertinent section from nf : # - Locale and Formatting. This is the date command output on my local system : That's it, case solved ! I disconnected and tried to reconnect. That created an unexpected 'positive' glitch - I found myself connected after refreshing the page.
I recreated the cluster several times by following those steps like that : sudo pg_createcluster -locale fr_FR.UTF-8 9.6 main I suspect that the system locale affects the database initialization. 15:57:36.995 CEST HINT: Perhaps you need a different "datestyle" setting. That's the postgresql error log : 15:57:34.838 CEST STATEMENT: insert into log(login, nom_mod, log_date, comment, ip) values ($1, $2, $3, $4, $5) RETURNING log_id
The error shows a strange thing - looks like the date is getting written in YDM format, which doesn't correspond to the default postgresql datestyle. When a user logs-in certain data is stored in the database and one of those details is date and time. When I log-in the same error reproduces on both machines - odd timestamp interpretation.
#Postgres set to datestyle iso mdyc install#
I try to install a web-application on a server (debian) and on a local machine (ubuntu). The problem of this issue has been identified and can be treated as resolved.
0 kommentar(er)
