Hello John,
Am 19.03.2012 14:57, schrieb jcbollinger:
> 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).that was my fault. The parameter "standard_conforming_strings" is not new, but since PostgreSQL 9.x the value "on" is default. > 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. The backslashes are not the problem, but \u will be handled as unicode escapes which should look like "\uXXXX" or "\UXXXXXXXX". I hoped that somebody would know the component which is creating the insert statement, because is wanted to do some more debugging before i file a bug. Regards, Dennis
signature.asc
Description: OpenPGP digital signature
