Re: backslash encoded data changed during upgrade?

From: Doug Hunley <doug(dot)hunley(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: backslash encoded data changed during upgrade?
Date: 2012-11-26 18:07:03
Message-ID: CALxYTP6k68q3q+PFvewH_f_4bYFmSFtMf-xCwDQVK-0VtBU_Zg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 26, 2012 at 12:22 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> They look like bytea fields, in which case the parameter you're
> looking for is bytea_output (which is 'hex' by default now, used to be
> 'escape').

YES! Thank you Magnus! This was exactly it.

--
Douglas J Hunley (doug(dot)hunley(at)gmail(dot)com)
Twitter: @hunleyd Web:
douglasjhunley.com
G+: http://goo.gl/sajR3

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2012-11-26 18:15:00 Re: Copy rows, remember old and new pkey
Previous Message Magnus Hagander 2012-11-26 17:22:57 Re: backslash encoded data changed during upgrade?