| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
The information from this article applies to changes introduced with PostgreSQL release 9.1 and JobScheduler 1.10.7. |
If you receive the error
| Code Block |
|---|
SCHEDULER-451 Database check failed, database is not useable. SCHEDULER-452 Database does not correctly store test values:
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~\ (written value)
\t\r\n !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~\\ (read value)
|
then the parameter standard_conforming_strings parameter is turned on and you are using a JobScheduler version that expects this parameter to be set to off.
This parameter is turned on by default since PostgreSQL 9.1.
The JobScheduler expected at the time JobScheduler releases older than 1.10.7 expected that this parameter is turned off.
We will change this behaviour, see This behaviour of the JobScheduler was changed with release 1.10.7.
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Until that happens, you can change the value of standard_conforming_strings in the postgresql.conf file or only for the JobScheduler user via following SQL:
...
See How can JobScheduler run with PostgreSQL 9-1 and newer? for more information and a workaround.