| From: | wambacher(at)posteo(dot)de |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: tuple concurrently updated |
| Date: | 2018-08-28 13:19:28 |
| Message-ID: | 2be8ebca-fecc-51f4-39d7-9869941c679a@posteo.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)free(dot)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 ?"
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pavan95 | 2018-08-28 13:24:55 | Re: How to get alerted automatically whenever a table structure is changed between Publisher and Subscriber in Logical Replication? |
| Previous Message | 066ce286 | 2018-08-28 13:10:05 | Re: tuple concurrently updated |