From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-02-27 01:09:07 |
Message-ID: | CAM3SWZQgntuwDtXn7nYE835rbVM8peYjSGhObQgOa0rgLY6aQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 26, 2014 at 5:06 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-02-27 01:44:33 | Re: jsonb and nested hstore |
Previous Message | Alvaro Herrera | 2014-02-27 01:06:55 | Re: jsonb and nested hstore |