On Wed, Feb 26, 2014 at 5:06 PM, Alvaro Herrera
<alvhe...@2ndquadrant.com> wrote:
>> I think that this is not a great idea. I think that we should do away
>> with the GUC, but keep the function hstore_print() so we can pretty
>> print that way. I don't believe that this falls afoul of the usual
>> obvious reasons for not varying the behavior of IO routines with a
>> GUC, since it only varies whitespace, but it is surely pretty
>> questionable to have this GUC's setting vary the output of hstore_out,
>> an IMMUTABLE function.
> I don't see this in the submitted patch.  What's going on?

I'm working off the Github branch here, as of an hour ago, since I was
under the impression that the patches submitted are merely snapshots
of that (plus I happen to strongly prefer not dealing with patch files
for something this big). Which submitted patch?

Peter Geoghegan

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to