Re: json indexing and data types

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>, Kaare Rasmussen <kaare(at)jasonic(dot)dk>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: json indexing and data types
Date: 2015-12-03 01:11:26
Message-ID: 565F96BE.9060209@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/2/15 7:06 PM, Merlin Moncure wrote:
> > The basics is, that I have a column with what is essentially json data; a
> > number of data structures of different depths. Perhaps 10 - 30 top
> levels,
> > and probably no more than 3, max 4 levels deep. In total there are some
> > hundred thousands of rows in each table. It would probably be best
> stored as
> > jsonb. Right now it's text, because it's only used by the application
> > itself.

After re-reading this part...

Are you in control of the JSON itself, and are the number of
permutations known in advance? It might be that something like table
inheritance is a better solution...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Florin Andrei 2015-12-03 01:24:24 loading data into cluster - can I daisy-chain streaming replication?
Previous Message Jim Nasby 2015-12-03 01:07:55 Re: plperlu stored procedure seems to freeze for a minute