Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
| От | Adrian Klaver |
|---|---|
| Тема | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) |
| Дата | |
| Msg-id | 201103010718.50601.adrian.klaver@gmail.com обсуждение |
| Ответ на | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) (Aleksey Tsalolikhin <atsaloli.tech@gmail.com>) |
| Список | pgsql-general |
On Monday, February 28, 2011 9:51:10 pm Aleksey Tsalolikhin wrote: > > Here is what I see: > > > > nspname | relname | tablesize > > | indexsize | toastsize | toastindexsize > > ------------------------+----------------------------------+------------+-- > ----------+------------+---------------- public | big > | 744 MB > > | 737 MB | 48 GB | 278 MB > > public | big | 503 MB > > | 387 MB | 99 GB | 278 MB > > Check out that toastsize delta. What makes up TOAST? How can I > compare the two TOAST tables in detail? > The compression/no compression thing tickled a memory. Run \d+ against the table in question. It should show a storage column with values for each field. Are any of those set to EXTERNAL instead of the default EXTENDED? -- Adrian Klaver adrian.klaver@gmail.com
В списке pgsql-general по дате отправления: