Error unexpected response

[aleksandrkazakovv]

Hello. I have next configuration:
Ubuntu 20.04
wal-g 2.0.1
PostgreSQL 15.5-1 + TimescaleDB 2.9.0
config for backup to local folder:
{ "WALG_FILE_PREFIX": "/tmp/wal-g-test-data", "PGDATA": "/var/lib/postgresql/15/main", "PGHOST": "/var/run/postgresql" }

config backup to s3(minio):
{ "WALG_S3_PREFIX": "s3://walg", AWS_S3_FORCE_PATH_STYLE: "true" "AWS_ENDPOINT": "http://192.168.1.20:9000", "AWS_ACCESS_KEY_ID": "*******", "AWS_SECRET_ACCESS_KEY": "******", "WALG_COMPRESSION_METHOD": "brotli", "WALG_DELTA_MAX_STEPS": "5", "PGDATA": "/var/lib/postgresql/15/main", "PGHOST": "/var/run/postgresql" }
when i start backup to local folder or to s3, i get same errors:
WARNING: 2024/01/31 22:00:38.334769 It seems your archive_command is not configured. This will cause inconsistent backup. Please consider configuring WAL archiving. INFO: 2024/01/31 22:00:38.337134 Running remote backup through Postgres connection. INFO: 2024/01/31 22:00:38.337144 Features like delta backup are disabled, there might be a performance impact. INFO: 2024/01/31 22:00:38.337146 To run with local backup functionalities, supply [db_directory]. INFO: 2024/01/31 22:00:38.339009 Starting remote backup ERROR: 2024/01/31 22:00:38.339145 unexpected response: &{%!t(string=ERROR) %!t(string=ERROR) %!t(string=42601) %!t(string=syntax error) %!t(string=) %!t(string=) %!t(int32=0) %!t(int32=0) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=repl_scanner.l) %!t(int32=237) %!t(string=replication_yyerror) map[]}
Can anybody to help me, what does it meen?

[x4m]

Hi Aleksandr,
Thank you for trying WAL-G. I see that you are using the remote backup feature. This is not the default way to perform a backup. Could you please try using the regular wal-g backup-push command with the %PGDATA% parameter? I suspect that one of the reasons of this issue is that the remote backup may be causing issues with TimescaleDB, but I don't have strong evidence to support this claim.

@sebasmannem Sebastian, could you please have a look at this? The Postgres response seems unusual.