| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | richard(dot)klaumann(at)gmail(dot)com |
| Subject: | BUG #16012: vacuum full, something weird |
| Date: | 2019-09-18 13:24:46 |
| Message-ID: | 16012-f3d6e43dad580a1f@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16012
Logged by: Richard Klaumann
Email address: richard(dot)klaumann(at)gmail(dot)com
PostgreSQL version: 9.5.3
Operating system: Centos 7.x
Description:
Hello,
First sorry for my english.
Today we store our byteas in tables. We are moving these files to
storages.
During the process we set the bytea column to null and execute vacum full
(in the table itself and in the table pg_catalog.pg_largeobject).
In some tables we continue with pg_total_relation_size> 24GB (practically
the initial size). Data in the toast table.
If I run a new vacuum full on the main table, the space is freed.
Can someone help me?
Sorry if it's not the correct list.
Thankful,
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-09-18 14:16:38 | Re: Restricted interval data type |
| Previous Message | Dmitry Dolgov | 2019-09-18 11:09:02 | Re: Bug: array starting index seems incorrect (different for 1D and 2D arrays) |