On Tue, Jul 31, 2012 at 9:07 AM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:
> On Tue, 2012-07-31 at 14:06 +0800, Craig Ringer wrote:
>> On 07/31/2012 01:50 PM, Guillaume Lelarge wrote:
>> >> Check the PgAdmin-III preferences; there may be an option to control its
>> >> preferred bytea format.
>> >>
>> > There's no option to control this.
>> >
>> Thanks for confirming that.
>>
>> Is it really best for PgAdmin-III to have a different default than Pg
>> its self?
>>
>
> Well, we didn't until we had an issue to get informations from the
> tgargs column of the pg_trigger catalog. I don't remember the details
> right now, and I still didn't check how psql works with this, so I may
> be wrong. The only way I could find to fix the issue was to set
> bytea_output to escape. It probably is specific to pgAdmin.
>
> If we can't fix this another way, we can have a workaround. We only need
> this setting for pgAdmin's browser. Not the query tool. It would be a
> nice and quick workaround.
I wouldn't call that a workaround, I would call it an actual fix. And
I would call the current state a bug, because it overrides the users
settings. Even if the user has changed it with e.g. ALTER ROLE SET,
pgadmin will override it.
We should try to keep the environment for the query tool connection as
clean as possible. So if it's reasonably easy to do this (I haven't
looked at the code, but I would assume it is), then I suggest doing
that *and* backpatching it so it'll go into the next version of the
stable branch.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
