| From: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: autovacuum doesnt run on the pg_toast_id table |
| Date: | 2019-01-17 20:18:29 |
| Message-ID: | CA+t6e1nBK6vHJSp39K9=DKsr-SyWZP02gzzC-XEUp7P9A8eoPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Got it, I didn't see the toast word in the command. Thanks !
On Thu, Jan 17, 2019, 10:17 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com
wrote:
> On 2019-Jan-17, Mariel Cherkassky wrote:
>
> > But you said that the threshold that is chosen for the toasted table is
> > identical to the originals table threshold right ?
>
> You can configure them identical, or different. Up to you.
>
> > Is that a normal behavior that the original table has 1000recrods but
> > the toasted has more than 10m?
>
> Sure -- each large record in the main table is split into many 2kb
> records in the toast table.
>
> > How can I set a different threshold for the toasted table ?
>
> Just choose a different value in the command I showed.
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2019-01-18 12:55:28 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
| Previous Message | Alvaro Herrera | 2019-01-17 20:16:59 | Re: autovacuum doesnt run on the pg_toast_id table |