Hello,
we found out that script contents are not properly displayed in the web UI
in Systems - Events - History (it's a perl page ...).
To reproduce:
- choose a system and go to Remote Command
- type in some script contents, e.g. a b c d e f g h
- schedule the command
- go to Events and click
Hi Johannes,
Can you please give me more information on the system where you are
experiencing this problem?
We had a bug with identical symptoms where the root cause was that the
defaults on how a particular object was stored (as ascii or as hex) in
Postgresql changed in newer versions of the
On Tue, Aug 14, 2012 at 12:18:39PM +0200, Johannes Renner wrote:
Hello,
we found out that script contents are not properly displayed in the web UI
in Systems - Events - History (it's a perl page ...).
To reproduce:
- choose a system and go to Remote Command
- type in some script
Johannes,
Could you ensure in /usr/share/pgsql/postgresql.conf that bytea_output =
'escape', and if not see if that corrects your problem?
-Stephen
On 08/14/2012 08:57 AM, Stephen Herr wrote:
Hi Johannes,
Can you please give me more information on the system where you are
experiencing
On 08/14/2012 03:36 PM, Stephen Herr wrote:
Johannes,
Could you ensure in /usr/share/pgsql/postgresql.conf that bytea_output =
'escape', and if not see if
that corrects your problem?
-Stephen
Thanks, setting this option fixes the problem on the postgres 9.1 database we
are using.
We
On Fri, Jun 15, 2012 at 08:28:04PM +0200, Miroslav Suchý wrote:
If you look at commit:
d8744d1693c1fc6e231278dd9a6537f269371192
and the code:
+if self.blob_map:
+for blob_var in self.blob_map.keys():
+ kw[blob_var] = kw[blob_var].replace('\\', '')
On Tue, Aug 14, 2012 at 03:53:08PM +0200, Johannes Renner wrote:
On 08/14/2012 03:36 PM, Stephen Herr wrote:
Johannes,
Could you ensure in /usr/share/pgsql/postgresql.conf that bytea_output =
'escape', and if not see if
that corrects your problem?
-Stephen
Thanks, setting this
