The old 'escape' encoding used by PostgreSQL 8.4 and prior was pretty
helpful for getting human-readable strings in psql. It seems this
functionality was removed in PostgreSQL 9.0. Was this an accident or
a deliberate decision? Could we get it back, please?
--
Florian Weimer
BF
Florian Weimer writes:
> The old 'escape' encoding used by PostgreSQL 8.4 and prior was pretty
> helpful for getting human-readable strings in psql. It seems this
> functionality was removed in PostgreSQL 9.0. Was this an accident or
> a deliberate decision? Could we get it back, please?
I thi
* Tom Lane:
> Florian Weimer writes:
>> The old 'escape' encoding used by PostgreSQL 8.4 and prior was pretty
>> helpful for getting human-readable strings in psql. It seems this
>> functionality was removed in PostgreSQL 9.0. Was this an accident or
>> a deliberate decision? Could we get it b
Florian Weimer writes:
> Put differently, I think it's rather odd that in 9.0, both
> encode(bytea_value, 'escape') and encode(bytea_value, 'hex') output
> hexadecimal values.
I don't believe that; encode produces text not bytea, so its result
is not affected by this setting.
* Tom Lane:
> Florian Weimer writes:
>> Put differently, I think it's rather odd that in 9.0, both
>> encode(bytea_value, 'escape') and encode(bytea_value, 'hex') output
>> hexadecimal values.
>
> I don't believe that; encode produces text not bytea, so its result
> is not affected by this settin
On 2010-12-06, Florian Weimer wrote:
> * Tom Lane:
>
>> Florian Weimer writes:
>>> The old 'escape' encoding used by PostgreSQL 8.4 and prior was pretty
>>> helpful for getting human-readable strings in psql. It seems this
>>> functionality was removed in PostgreSQL 9.0. Was this an accident or
