| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> |
| Cc: | "pgsql-jdbc(at)lists(dot)postgresql(dot)org" <pgsql-jdbc(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Duplicate tables information through metadata queries |
| Date: | 2021-09-08 22:08:40 |
| Message-ID: | CAKFQuwavFiZLEr+eB3o5VZacFoQMRaGWgDzxjj2LFC7xNgO1Fg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wednesday, September 8, 2021, ldh(at)laurent-hasson(dot)com <
ldh(at)laurent-hasson(dot)com> wrote:
>
>
> Vacuum Full doesn't rebuild indices??? I always thought it did as per the
> docs on https://www.postgresql.org/docs/13/routine-vacuuming.html.
>
Yeah, it has to rebuild the indexes since the physical locations of
everything change during a vacuum full. But doing that on the user table
will not help - the oid stays the same and that is the only link (an
indirect one at that) to the problem comment data. Doing it on the catalog
might help…never tried myself, vacuum full or a independent reindex.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-09-08 22:19:24 | Duplicate tables information through metadata queries |
| Previous Message | Andrew Dunstan | 2021-09-08 22:04:49 | Re: Duplicate tables information through metadata queries |