RE: Duplicate tables information through metadata queries

>
> From: David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
> Sent: Wednesday, September 8, 2021 17:44
> To: ldh(at)laurent-hasson(dot)com
> Cc: pgsql-jdbc(at)lists(dot)postgresql(dot)org
> Subject: Re: Duplicate tables information through metadata queries
>
> On Wednesday, September 8, 2021, David G. Johnston <mailto:david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wednesday, September 8, 2021, mailto:ldh(at)laurent-hasson(dot)com <mailto:ldh(at)laurent-hasson(dot)com> wrote:
>
> VACUUM FULL FREEZE ANALYZE  PEOPLE.contact; 
>
> No change.
>
> That is not surprising.  I’m lretty sure that also doesn’t cause indexes to be rebuilt.
>
>
> Sorry, by “the table” I meant pg_description, i.e. the one with the bad data.
>
>  David J.
>

Hello David,

I figured out what you meant with "-bugs" and posted there a few minutes ago. Thank you for the pointer.

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.

I did try a reindex anyways on my table and that didn't do anything. I also tried a reindex/vacuum on the PG_CATALOG.pg_description table but that didn't work: I get a lock timeout in both cases. I don't know if that's possible.

In any case, thank you for your help... I have posted to the "bugs" mailing list and hope to get some help there.

Thank you,
Laurent.