Re: tuple concurrently updated

Поиск
Список
Период
Сортировка
От wambacher@posteo.de
Тема Re: tuple concurrently updated
Дата
Msg-id 2be8ebca-fecc-51f4-39d7-9869941c679a@posteo.de
обсуждение исходный текст
Ответ на Re: tuple concurrently updated  (066ce286@free.fr)
Ответы Re: tuple concurrently updated  (066ce286@free.fr)
Re: tuple concurrently updated  (pavan95 <pavan.postgresdba@gmail.com>)
Список pgsql-admin
because it's an OpenStreetMap Full planet database, which is huge (~ 2
TB), i don't have many backups. the last is from 20180608

ok, i can restore that and reload the incremential updates or reload
full data starting from raw data. both will need some days.

if i could get rid of the bad data-record, it's much easier to recover that.

Running a vacuum or a vacuum full, is my last try.

Regards
walter


Am 28.08.2018 um 15:10 schrieb 066ce286@free.fr:
> BTW you have data corruption.
>
> So forget your problem about concurrent updates ; that's not the clue.
>
> Your new question should be how to recover corrupted table.
>
> Sorry, I've no skill for that problem other that "how ran your backups/archivelogs ?"
>




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

Предыдущее
От: 066ce286@free.fr
Дата:
Сообщение: Re: tuple concurrently updated
Следующее
От: pavan95
Дата:
Сообщение: Re: How to get alerted automatically whenever a table structure ischanged between Publisher and Subscriber in Logical Replication?