Re: ERROR: unexpected chunk number 0 (expected 1) for toast value76753264 in pg_toast_10920100

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: ERROR: unexpected chunk number 0 (expected 1) for toast value76753264 in pg_toast_10920100
Дата
Msg-id 20180118013957.GD29962@paquier.xyz
обсуждение исходный текст
Ответ на Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
On Wed, Jan 17, 2018 at 12:16:19PM -0500, Tom Lane wrote:
> The basic thrust of these messages is "I'm reading what should be
> sequentially numbered data chunks for this toast OID, and the sequence
> numbers are wrong".  Both of these instances could be explained by
> duplicate toast rows (or duplicate index entries pointing at one row),
> though of course that would just move to the next question of how it
> got that way.

Good point here. This could be a consequence of freeze-the-dead whose
fix will be available in the next round of minor releases.
--
Michael

Вложения

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

Предыдущее
От: Jacek Kołodziej
Дата:
Сообщение: Re: READ COMMITTED vs. index-only scans
Следующее
От: Nikolay
Дата:
Сообщение: Partitioning constraints vs before-trigger