Server table rows permanently fixed (cannot be deleted or truncated)

Поиск
Список
Период
Сортировка
От Fred Williams
Тема Server table rows permanently fixed (cannot be deleted or truncated)
Дата
Msg-id CAJ8mXMoKCyXhxo=d_qjxvSNSC8w1yDbw-WRgSKz40_bei8EzcA@mail.gmail.com
обсуждение исходный текст
Ответы Re: Server table rows permanently fixed (cannot be deleted or truncated)
Re: Server table rows permanently fixed (cannot be deleted or truncated)
Список pgsql-bugs
Дерево обсуждения
PostgreSQL version 12.2

Problem
I am unable to delete or edit a specific range of table rows (I'll call them corrupted rows) for a specific primary key. If I truncate the entire table, the corrupted rows remain. In the corrupted rows, I can successfully update non-primary key fields, but not primary-key fields.

Miscellaneous
  1. The problem does not occur on a test server using the same exact table. 
  2. If I rename the table, I can remove the corrupted rows and/or update the primary keys (such as changing the DateTime). However, when I rename it back, the corrupted rows reappear!
Table info

CREATE TABLE public."NCAASchedule" (
"GameDateTime" timestamp NOT NULL,
"Week" int2 NOT NULL,
"HomeTeam" int2 NOT NULL,
"AwayTeam" int2 NOT NULL,
"Line" numeric(5, 1) NULL,
"OverUnder" numeric(5, 1) NULL,
"HomeTeamScore" int2 NULL,
"AwayTeamScore" int2 NULL,
"OpeningLine" numeric(5, 1) NULL,
"BowlID" int2 NULL,
"Control" int2 NULL,
CONSTRAINT ncaaschedule_pk PRIMARY KEY ("GameDateTime", "Week", "HomeTeam", "AwayTeam")
);

Thanks for any help you can provide.

Fred Williams

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
Следующее
От: hubert depesz lubaczewski
Дата:
Сообщение: Re: WAL segments removed from primary despite the fact that logical replication slot needs it.