On Mar 18, 9:53 am, Dennis Hoppe <dennis.ho...@debian-solutions.de>
wrote:
> i did some debugging and found out that with PostgreSQL 8.4 everything
> works as expected.
>
> If i use PostgreSQL 9.1, the following lines are responsible for the
> error message.
>
> PS1='${debian_chroot:+($debian_chroot)}\[<%= t_color
> -%>\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
> PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
> PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
>
> I spoke to our DBA and he told me that with PostgreSQL 9.1 the parameter
> "standard_conforming_strings" was introduced. If i set this parameter to
> off, everyhting works as expected again.
I am glad you discovered a solution. Your DBA is incorrect that the
standard_conforming_strings parameter is new in PG 9, however. It is
documented at least as far back as version 8.2, and with the same
default value (off).
It appears that with standard_conforming_strings on, Puppet was
attempting to insert your file content as a PG 'escaped' string
instead of as a literal string. Perhaps it did so because of the
backslashes in the value, but whatever the reason, that looks like a
bug to me, and I encourage you to file an issue about it.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
