| 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 21:23:41 |
| Message-ID: | CAKFQuwanxv00PFA+T5G0DmiVM1xTBZovW0c80ZLLbh=kCxtn5A@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:
>
>
> I am not sure about your solution for cleanup however. Do you mean?
>
>
> COMMENT ON TABLE PEOPLE.Contact IS 'Blah';
Yes
>
>
> This doesn't seem to have any effect except updating the comment for the
> second row above. Should I just delete the record from the table for the
> tables affected? I know this is generally not good practice AT ALL... 😊
Maybe reindex the table first, then do comment on? It might be worth
posting this to -bugs and solicit suggestions on getting out the situation
from a better targeted audience.
> Also, you mention data corruption, but would that survive a backup/restore?
>
>
Both rows should be copied out on backup and copied back in during restore.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ldh@laurent-hasson.com | 2021-09-08 21:27:42 | JDBC Meta-data performance for Foreign Keys |
| Previous Message | ldh@laurent-hasson.com | 2021-09-08 21:15:10 | RE: Duplicate tables information through metadata queries |