From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "bubba postgres *EXTERN*" <bubba(dot)postgres(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_largeobject vs pg_toast_XXXX |
Date: | 2011-08-03 07:47:56 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C206B93593@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
bubba postgres wrote:
> No takers?
> Some background I've changed my TOAST type from EXTENDED to MAIN.
> After some changes on my DB I notice that where I used to have a large
pg_toast_XXXXX table, I
> now have a large pg_largeobject table.
> Can't find an explanation of the difference between the two, could
someone enlighten me?
There is no connection between TOAST tables and pg_largeobject, which
holds large objects.
Changing TOAST strategy from EXTENDED to MAIN will give you a larger
main table and a smaller TOAST table.
See
http://www.postgresql.org/docs/current/static/storage-toast.html
Try \lo_list at your psql prompt to see why your large object table
is big.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Graham | 2011-08-03 09:47:24 | Vacuum as "easily obtained" locks |
Previous Message | Rory Campbell-Lange | 2011-08-03 06:58:17 | Re: Problem with selecting arrays in set-returning plpgsql function |