Andrey Borodin
Andrey Borodin
> So the sdk fixed something which affects our S3 instance? Is there a way to find out what? You can bisect first WAL-G release that does not hang and...
What is first WAL-G version that does not hang?
Hi! Thanks for reporting! Sounds really scarry. Can you please check indexes with amcheck? If possible with bt_index_check_parent(). Messages from this utility can help analyze what happened.
I would suggest avoid fixing problem with REINDEX: it's better to track source of the corruption before doing this.
Can you please check backup source with amcheck too?
We do amcheck+reindex(for indexes that failed) during trusty->bionic migration. And do not use different distros across nodes.
1. Restore copy of a cluster on new Ubuntu 2. Identify collation-dependent indexex with amcheck 3. after upgrade - reindex those indexes. (see latest PG release if you can REINDEX...
Hi Dennis! Last time when I got this error was when I mistype AWS_SECRET_ACCESS_KEY, added whitespace at the end. I do not use AWS, I use S3 compatible Yandex Object...
you can set WALG_LOG_LEVEL=DEVEL or use strace or modify source codes, the compilation is not that hard....
@keefien feel free to send a PR woith proposed change. if you need assistance with code plz ask your questions here, in Telegram or Slack dev chat.