On Mon, 2010-08-16 at 11:40 -0400, Christopher Browne wrote:
> On Mon, Aug 16, 2010 at 11:21 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> > On Mon, Aug 16, 2010 at 11:05 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> Andrew Dunstan <andrew@dunslane.net> writes:
> >>> If BSON is simply in effect an efficient encoding of JSON, then it's not
> >>> clear to me that we would want another type at all. Rather, we might
> >>> want to consider storing the data in this supposedly more efficient
> >>> format, and maybe also some conversion routines.
> >>
> >> Hmm, that's an interesting plan ...
> >
> > It is interesting, but I'm not sure that it will actually work out
> > well in practice. If what we want to do is compress JSON, TOAST will
> > do that for us without any additional code, and probably a lot more
> > efficiently. Of course, until someone tests it, we're just
> > speculating wildly.
>
> Yep, that was exactly what struck me. TOAST is quite likely to be a
> good answer for this.
Except: How much JSON data will actually be TOASTed?
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt