| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: TOASTed size |
| Date: | 2007-12-05 08:55:11 |
| Message-ID: | 4756676F.3050505@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
>
> That sounds more like what I was after.
>
> So let me check my understanding: For TOASTed data pg_column_size()
> tells you how many bytes the column value occupies when decompressed. So
> there isn't any way of finding out how many bytes a column value
> actually occupies when it is both compressed and external?
>
>
I dimly recall getting confused by this when writing this guy:
From what I can see: pg_column_size calls toast_datum_size for any
variable length attribute - and then gets the external pointer and
returns its va_extsize component (which looks to me like the
*compressed* size.)
Cheers
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-12-05 09:35:13 | Re: TOASTed size |
| Previous Message | Simon Riggs | 2007-12-05 08:35:31 | Re: TOASTed size |