| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Manu Saxena <manu(dot)saxena(at)lavainternational(dot)in> |
| Subject: | Re: Avg/max size of these JSON docs in Postgres |
| Date: | 2021-10-12 18:14:46 |
| Message-ID: | 585459.1634062486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Michael Lewis <mlewis(at)entrata(dot)com> writes:
> Just to confirm- The compression associated with TOAST is only if the value
> can fit in line, right? Columns don't get stored out-of-line in a toast
> table as a compressed value as I read the documentation. I suppose that
> would make reads a bit crazy.
The default behavior is first to compress any large field value(s),
and then if the row is still too big, push them out-of-line in
compressed form. You can modify that strategy on a per-column
basis if need be, but I've seldom heard good reasons to.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2021-10-12 18:51:13 | Re: Avg/max size of these JSON docs in Postgres |
| Previous Message | Michael Lewis | 2021-10-12 17:53:09 | Re: Avg/max size of these JSON docs in Postgres |