| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rama Krishnan <raghuldrag(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Vacuum full issue |
| Date: | 2023-02-16 19:28:02 |
| Message-ID: | CAKFQuwZ70znrdfXAzOytdBX2Q6-1AeKhdBJr_UPUmtAKD5tixA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 16, 2023 at 12:24 PM Rama Krishnan <raghuldrag(at)gmail(dot)com> wrote:
> 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?
>
No, vacuum full is not designed to destroy xml data that has been stored in
the database.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2023-02-16 19:29:52 | Re: Vacuum full issue |
| Previous Message | David G. Johnston | 2023-02-16 19:22:04 | Re: How to avoid Trigger ping/pong / infinite loop |