Re: json on child table or not

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: PegoraroF10 <marcos(at)f10(dot)com(dot)br>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: json on child table or not
Date: 2019-05-31 17:08:03
Message-ID: CAHOFxGrP-gBKCYeCS6wXs=yHUbHd-5uoO+dDiV-4L971Zu5xjQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message PegoraroF10 2019-05-31 18:21:23 Re: json on child table or not
Previous Message Michael Lewis 2019-05-31 17:00:57 Re: Feature request (or at least discussion): enable autovaccum on temp tables