Re: interpret bytea output as text / double encode()

> > # select encode(encode(column, 'escape'), 'escape')

> Any  chance you can encode() into temp table then encode() the result.

Don't think so, PostgreSQL will recognize the temp column either as text
or as bytea and then refuse either the insert or the encode() because of
a type mismatch.

Any workaround for this would most likely solve my original problem
without the use of a temp table.

Stefan