On February 14, 2017 9:02:14 PM PST, neha khatri <nehakhat...@gmail.com> wrote: >On Wed, Feb 15, 2017 at 10:04 AM, neha khatri <nehakhat...@gmail.com> > wrote:. >> >> >>> Attached are two options for doing that. One overrides bytea_output >>> locally where-ever needed, and the other overrides it for the entire >>> 'regression' database. >>> >> >> The solution that overrides bytea_output locally looks appropriate. >It may >> not be required to change the format for entire database. >> Had there been a way to convert bytea_output from 'hex' to 'escape' >> internally, that could have simplified this customization even more. >> > >Well, the conversion from 'hex' to 'escape' is available using the >function >encode(). >So the queries that are failing due to the setting bytea_output = >escape, >can be wrapped under encode(), to obtain the result in 'escape' format. >Here is another way to resolve the same problem. The patch is attached.
I don't quite see the point of this - there's a lot of settings that cause spurious test failures. I don't see any point fixing random cases of that. And I don't think the continual cost of doing so overall is worth the minimal gain. What's your reason to get this fixed? Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
