| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Rama Krishnan <raghuldrag(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Vacuum full issue |
| Date: | 2023-02-16 19:29:52 |
| Message-ID: | 1dbe2a36-6432-13ff-21b6-7b82158004be@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/16/23 05:18, Rama Krishnan wrote:
> Hi All,
>
> One of my friend project they did vacuum full last week since one of
> the table column data type were CLOB after that activity the dev team
> found out some of the data were missing or corrupt (XML) , please
> explain me will vacuum full have any limitation like that?
I'm guessing this has to do with whatever condition caused then to
decide to do VACUUM FULL in the first place.
Why did they do the VACUUM FULL?
>
> Thanks
> Ramakrishnan
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-02-16 19:38:27 | Re: Support logical replication of DDLs |
| Previous Message | David G. Johnston | 2023-02-16 19:28:02 | Re: Vacuum full issue |