| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-10 12:39:04 |
| Message-ID: | 20140210123904.GA10885@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-02-10 07:27:59 -0500, Andrew Dunstan wrote:
> On 02/10/2014 05:05 AM, Andres Freund wrote:
> >I'd suggest making the format discernible from possible different future
> >formats, to allow introducing a proper binary at some later time. Maybe
> >just send a int8 first, containing the format.
> >
>
> Teodor privately suggested something similar. I was thinking of just
> sending a version byte, which for now would be '\x01'. An int8 seems like
> more future-proofing provision than we really need.
Hm. Isn't that just about the same? I was thinking of the c type int8,
not the 64bit type. It seems cleaner to do a pg_sendint(..., 1, 1) than
to do it manually inside the string.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-02-10 13:18:06 | Re: jsonb and nested hstore |
| Previous Message | Andrew Dunstan | 2014-02-10 12:27:59 | Re: jsonb and nested hstore |