Table of Contents |
---|
| outlinh1. true |
---|
| outlinh1. true |
---|
1 | printablefalse |
---|
2 | stylh1. none |
---|
3 | indent20px |
---|
|
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 is turned on.
This parameter is turned on by default since PostgreSQL 9.1.
The JobScheduler expected at the time that this parameter is turned off.
We will change this behaviour, see
Jira |
---|
server | SOS JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 6dc67751-9d67-34cd-985b-194a8cdc9602 |
---|
key | JS-781 |
---|
|
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:
Code Block |
---|
ALTER USER [scheduler_user] SET standard_conforming_strings = off;
|