-
Notifications
You must be signed in to change notification settings - Fork 571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #9244] String escape problem with PostgreSQL >= 9.1 and standard_conforming_strings=on #2811
Comments
Updated by gbeutner on 2015-05-11 05:54:23 +00:00
Which PostgreSQL version are you using? |
Updated by gbeutner on 2015-05-11 06:09:47 +00:00
This probably has to do with the fact that the default value for standard_conforming_strings was changed to ON in PostgreSQL 9.1 - which would indicate that this is most likely a bug in Icinga. |
Updated by cramm on 2015-05-11 14:40:31 +00:00 PostgreSQL version is 9.1 (9.1.15-0+deb7u1 Debian package.) |
Updated by mfriedrich on 2015-06-18 09:05:56 +00:00
|
Updated by mfriedrich on 2015-06-23 13:30:50 +00:00
|
Updated by mfriedrich on 2015-07-20 11:18:31 +00:00 Setting standard_conforming_strings=off in postgresql.conf makes it work again:
Using the default on postgresql-9.4.4-1.fc22.x86_64 the error is reproducible:
The problem here is the backslash at the end of the string, which gets taken into account as quote escaping. Proposed solutionstandard_conforming_strings=off on connect. |
Updated by mfriedrich on 2015-08-03 13:22:19 +00:00
|
Updated by mfriedrich on 2015-08-04 07:40:56 +00:00
|
Updated by mfriedrich on 2015-08-04 07:41:02 +00:00
|
Updated by mfriedrich on 2015-09-05 12:08:09 +00:00
More references: http://grokbase.com/t/postgresql/pgsql-general/094qmjcvw2/standard-conforming-strings-and-pg-escape-string I've already implemented and tested a fix on my F22 box with PostgreSQL 9.4. |
Updated by mfriedrich on 2015-09-05 12:10:04 +00:00
Applied in changeset fa6c0fe. |
Updated by mfriedrich on 2015-09-05 13:36:16 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9244
Created by cramm on 2015-05-09 12:27:23 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-09-05 12:10:04 +00:00)
Target Version: 2.3.10
Last Update: 2015-09-05 13:36:16 +00:00 (in Redmine)
Scenario:
* Postgres IDO module in use
Steps
Create a service for a general disk space check:
icinga2.log excerpt:
Note how the check_disk Windows plugin sends in its output a ``'Failed to access drive at E:\'`` error message (which doesn't happen when one executes it manually, but that's another topic possible for another issue).
That message somehow reachs the IDO DB unescaped.
Changesets
2015-09-05 12:08:35 +00:00 by mfriedrich fa6c0fe
2015-09-05 13:27:41 +00:00 by mfriedrich e06375d
Relations:
The text was updated successfully, but these errors were encountered: