| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>, Claes Jakobsson <claes(at)surfar(dot)nu>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Jan Urbański <wulczer(at)wulczer(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Jan Wieck <janwieck(at)yahoo(dot)com> |
| Subject: | Re: JSON for PG 9.2 |
| Date: | 2012-01-20 00:29:41 |
| Message-ID: | AB5CF1EC-B8FD-44FB-B67A-3188E70343C0@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 19, 2012, at 4:27 PM, Robert Haas wrote:
> I think the real fix for this problem is to introduce an
> infrastructure inside the database that allows us to have different
> columns stored in different encodings. People use bytea for that
> right now, but that's pretty unfriendly: it would be nice to have a
> better system. However, I expect that to take a lot of work and break
> a lot of things, and until we do it I don't feel that compelled to
> provide buggy and incomplete support for it under the guise of
> implementing a JSON datatype.
+1 This seems like a reasonable compromise and course of action, especially if someone is interested in taking on column-level encodings at some point in the next year or two.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-01-20 01:02:29 | Re: WIP -- renaming implicit sequences |
| Previous Message | Robert Haas | 2012-01-20 00:27:01 | Re: JSON for PG 9.2 |