| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Ajinkya Tankhiwale <ajinkya(dot)tankhiwale(at)tcs(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18002: Duplicate entries of row possible even after having primary key |
| Date: | 2023-07-03 01:06:56 |
| Message-ID: | CAH2-WznhY6s1jwbhTnqaoWaGrTcXdVruvVCdCoF4EAus5j1-NA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Jul 2, 2023 at 2:53 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> It might be best if you start again and explain the problem and
> include the table name of the table that is actually causing the
> issue. Use psql instead of pgAdmin and show us the output of:
>
> \d name_of_the_problem_table
They're on 14, so I suggest that pg_amcheck be used for this.
Ajinkya: Something like this ought to do it:
pg_amcheck --install-missing --heapallindexed -d postgres
What does that command output? Can you let us know?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-07-03 02:15:02 | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |
| Previous Message | Thomas Munro | 2023-07-02 22:27:18 | Re: BUG #18009: Postgres Recovery not happening |