| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | AI Rumman <rummandba(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: why does the toast table exist? |
| Date: | 2011-02-17 03:33:36 |
| Message-ID: | 20110217033336.GA6101@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 16, 2011 at 02:36:03PM +0600, AI Rumman wrote:
> I have no idea why the TOAST table exists for audit_trial table.
>
> \d audit_trial
> Table "public.audit_trial"
> Column | Type | Modifiers
> ------------+-----------------------------+-----------
> auditid | integer | not null
> userid | integer |
> module | character varying(255) |
> action | character varying(255) |
> recordid | character varying(20) |
> actiondate | timestamp without time zone |
Supposing your encoding is UTF8, each character can consume up to four bytes. A
row could use up to around 4 + 4 + 4*(255+255+20) + 8 bytes, which is large
enough to be toastable at the default block size.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-02-17 04:31:06 | Re: question regarding full_page_write |
| Previous Message | Gianni Ciolli | 2011-02-17 00:16:55 | Re: Query sought with windowing function to weed out dense points |