Re: json on child table or not - Mailing list pgsql-general

From Michael Lewis
Subject Re: json on child table or not
Date
Msg-id CAHOFxGrP-gBKCYeCS6wXs=yHUbHd-5uoO+dDiV-4L971Zu5xjQ@mail.gmail.com
Whole thread Raw
In response to json on child table or not  (PegoraroF10 <marcos@f10.com.br>)
Responses Re: json on child table or not
List pgsql-general
How big does the data stored in that field get? More than 2KB? Real question- is it getting stored plain, compressed inline, or toasted? Have you set the storage strategy/type, or is it the "extended" default behavior that compresses and then stores in the toast table if still more than 2000 bytes?

Always joining on a field that is toasted and compressed is going to be considerably slower than a discrete field. Do you have an index (or several) on the json field values? Also, are we actually talking about jsonb?

pgsql-general by date:

Previous
From: Michael Lewis
Date:
Subject: Re: Feature request (or at least discussion): enable autovaccum ontemp tables
Next
From: PegoraroF10
Date:
Subject: Re: json on child table or not