Andrey Borodin
Andrey Borodin
wal-g_pg_remote_backup_test | ERROR: 2024/10/29 10:27:37.866973 expect ready_for_query, got *pgproto3.CommandComplete This is not a flap…
Luckily only real failures are in remote backup. Maybe, @sebasmannem can shed some light on what happened?..
@NikolayS this issue is about MS SQL...
Hi! You can kill WAL-G with -SIGABRT to see what it is doing. It will print backtraces which might help to understand what S3 calls are hanging.
Also you can try S3_USE_LIST_OBJECTS_V1=true to see if anything changes.
```wal-g backup-list``` should iterate on all files with special prefix. Normally there's only 1 files per backup is listed. here's from my prod ``` [PROD]user@hostname~ # time wal-g backup-list >...
OK, if this is a regression in v3.0.1 we still need to fix it. this "GET /?list-type=2&max-keys=1 HTTP/1.1" seems like an undelimited listing. Can you please do a SIGABRT when...
Thanks! "github.com/wal-g/wal-g/pkg/storages/s3.(*Folder).Validate(0x25de058?)" gotcha @Themplarer can you please take a look at those backtraces ^^^ ... they seem to list waaay to much than expected during connection valication. It looks like...
@Themplarer Ugh... I got several questions regarding validation. Is it only affecting S3? Setting S3_SKIP_VALIDATION suggests it is, but just to be sure. It seems like we are validating storage...
Maybe we can just provide a command ```wal-g validate storage``` or something like that? We try to avoid messing with filesystem to save our stuff. and maybe have this validation...