I can also confirm the workaround is effective as well.
On Mon, Jun 3, 2013 at 1:42 PM, Paul Robert Marino <[email protected]>wrote: > > I can confirm I can reproduce the same issue with spacewalk 1.9 and > PostgreSQL 9.1. > > > > > On Mon, Jun 3, 2013 at 1:02 PM, new_user <[email protected]> wrote: > >> Thank you for reply. We are using Postgesql 9.2 with default settings. >> As I've read now, in psql 9.0 and later bytea_output is set to 'hex' by >> default. But in earlier version (8.x) it was set to 'escape ' >> Does it means that I have to switch this setting to 'escape', or I have >> to do something more? >> >> I think that I'm not alone who is using postgresql 9.x ... >> >> >> 2013/6/3 Michael Mraka <[email protected]> >> >>> Михаил wrote: >>> % Hello! I have a problem on my spacewalk 1.9 installation without >>> depending on target system: >>> % >>> % When I send a remote command on some target system, the command >>> executes successfully, but the output showed on the web-page looks like >>> some one-line hash: >>> % x544553540a4c696e7578206f62732e72736c2e6c6f632032...<many_symbols> >>> % >>> % Do anybody knows - what is the reason of this and how to fix it? >>> % Thank you. >>> >>> What's your postgresql version? >>> Could it be possible that you have non-standard bytea_output set? >>> >>> Regards, >>> >>> -- >>> Michael Mráka >>> Satellite Engineering, Red Hat >>> >>> _______________________________________________ >>> Spacewalk-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/spacewalk-list >> >> >> >> _______________________________________________ >> Spacewalk-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> > >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
