| From: | Artem Tomyuk <admin(at)leboutique(dot)com> |
|---|---|
| To: | Keith <keith(at)keithf4(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: how to shrink pg_attribute table in some database |
| Date: | 2018-03-26 13:43:51 |
| Message-ID: | CANYYVq+_vGDAu26Ze46RsPdiBrW8AC=RakPZzn89kDo_tqnTmA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thanks for quick response, Keith.
Can you explain your point more deeply, why its a bad idea to do
backup/restore of pg_attribute?
2018-03-26 16:41 GMT+03:00 Keith <keith(at)keithf4(dot)com>:
>
>
> On Mon, Mar 26, 2018 at 9:35 AM, Artem Tomyuk <admin(at)leboutique(dot)com>
> wrote:
>
>> Hi, Gurus!!!!
>>
>> Maybe someone knows what is the best way to shrink pg_attribute in size?
>> Maybe backup and restore of this table will sanitize "dead" records in it?
>> Or only full vacuum can help in this situation?
>>
>> Thanks!
>>
>
> VACUUM FULL would be the way to go if bloat is the issue you're trying to
> fix. Trying to backup up & restore a single system catalog would not be
> recommended.
>
> Keith
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Artem Tomyuk | 2018-03-26 14:15:14 | Re: how to shrink pg_attribute table in some database |
| Previous Message | Keith | 2018-03-26 13:41:12 | Re: how to shrink pg_attribute table in some database |