Thanks, everyone, for the swift and clear responses. It's good to know
that I did understand things correctly!
Reuven
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
"Reuven M. Lerner" writes:
> My client is concerned that the internal representation has changed, and
> is asking me for a script that will change the representation, in order
> to save space (since hex occupies less space than octal).
This is complete nonsense. The internal representation is
"Reuven M. Lerner" Sunday 20 February 2011 12:31:09
> Hi, everyone. I've got a client who is planning to upgrade from
> PostgreSQL 8.3 to 9.0 in the coming weeks. They use a lot of tables
> with bytea columns. They're worried about the switch from octal to hex
> formats for bytea data.
>
>
>
al-ow...@postgresql.org] On Behalf Of Reuven M. Lerner
Sent: Sunday, February 20, 2011 6:31 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Questions about octal vs. hex for bytea
Hi, everyone. I've got a client who is planning to upgrade from PostgreSQL 8.3
to 9.0 in the coming weeks. They us
Reuven M. Lerner wrote:
> So I've told them that I don't think that anything is necessary for
> either input or output, except (perhaps) to set bytea_output in its
> backward-compatibility mode. But I wanted to check with people here,
> just to double-check my understanding.
You are right,
Hi, everyone. I've got a client who is planning to upgrade from
PostgreSQL 8.3 to 9.0 in the coming weeks. They use a lot of tables
with bytea columns. They're worried about the switch from octal to hex
formats for bytea data.
Based on everything I know and have read, the change is only fo
