...
Server Variable standard_conforming_strings
Since For Postgres version 9.1 and newer the parameter standard_conforming_strings variable is turned set to on.
It This parameter controls whether or not ordinary string literals ('...') treat backslashes literally as specified in the SQL standard. This behaviour is different to versions before the behaviour of Postgres versions older than 9.1 and JobScheduler will will cause JobScheduler releases older than 1.10.5 to throw an exception. To avoid this, turn
The following workaround is available for users JobScheduler releases older than 1.10.5 working with Postgres version 9.1 and newer:
Turn off standard_conforming_strings in your PostgresSQL configuration.
For those who do not want to change this globally, this setting can be changed
...
for individual users:
Code Block language sql alter user scheduler set standard_conforming_strings = off
Since JobScheduler release 1.10.5 the default standard_conforming_strings = on is required.
| Jira | ||||||
|---|---|---|---|---|---|---|
|
The behavior of JobScheduler was modified with release 1.10.5 to take account of the standard_conforming_strings variable being set to on. Users of older JobSchedulers that have implemented the workaround described above and are updating to release 1.10.5 or newer should change the Postgres standard_conforming_strings variable back to the default on setting. The JobScheduler will not start if this is not done.
Server Variable bytea_output
...
| Code Block | ||
|---|---|---|
| ||
alter user scheduler set bytea_output = 'escape' |