| 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 19:52:43 |
| Message-ID: | CAKFQuwYD6TY4i78rZBzLB9eQSADL4uE++ZZ1WVwtVCRb6k8wEQ@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:
>
> The only difference I saw was in the “remarks” for the two tables, with
> one of them saying "btree comparison function" which is strange.
>
>
>
This would seem to indicate that the catalog pg_description has two rows
for this particular table and thus the join to it [1] causes the single
pg_class entry to become duplicated.
Per the comment command page each object gets at most one comment so having
multiples in the catalog is data corruption. If you confirm that you do
indeed have duplicates hopefully issuing create comment on the problematic
records clears up the issue.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ldh@laurent-hasson.com | 2021-09-08 21:15:10 | RE: Duplicate tables information through metadata queries |
| Previous Message | ldh@laurent-hasson.com | 2021-09-08 19:13:01 | Duplicate tables information through metadata queries |