Le 25/09/2010 01:09, Dave Page a écrit : > On Fri, Sep 24, 2010 at 11:54 PM, Guillaume Lelarge > <guilla...@lelarge.info> wrote: > >> Much better. So, the only way to fix this, AFAICT, is to set bytea_ouput >> to "escape" when connected to a 9.0 server. My question is this: should >> I set the parameter at the connection start, or should I set and unset >> it during the search of triggers? The latter is less error prone, but >> requires to execute three more queries (SHOW bytea_output, SET >> bytea_output TO escape, SET bytea_output TO old_value). > > Please set at connection. The old output is what all the rest of the > code expects (if anywhere does expect it), so I can't imagine it would > break anything. >
OK, that was also my favorite solution. Just pushed my commits on 1.12 and master. Thanks. -- Guillaume http://www.postgresql.fr http://dalibo.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
