Bug 855119

Description of problem:
If you are using the PostgreSQL database and a certain number of unknown other conditions are met, then config file and kickstart script contents appears corrupted in the webui. Unfortunately it is impossible to reproduce on some (most?) systems, due to some unknown variables. 

How reproducible:
On some systems, always, on other systems, never.

Steps to Reproduce:
1. View the contents of any config file or kickstart script in the webui
  
Actual results:
Contents are corrupted / are hex numbers instead of characters

Expected results:
File contents are displayed

Additional info:
This is due to the addition of a new and different default output style for bytea type fields in Postgres 9.0. In 9.0 the default output type is hex digits, whereas before then the only and default output type for bytea fields was the "escape" output type. All code in Spacewalk assumes it is receiving the "escape" type response from the bytea field, so if the database returns hex instead it doesn't know how to parse it and displays improperly.

The fix for this is really simple. We just need to set the tell the database to always use the escape output type for bytea fields:

ALTER DATABASE database SET bytea_output = 'escape';