Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup failed (the value of segment_size is greater than 2G) #609

Open
qiuwenhuifx opened this issue Aug 24, 2023 · 3 comments
Open

Backup failed (the value of segment_size is greater than 2G) #609

qiuwenhuifx opened this issue Aug 24, 2023 · 3 comments

Comments

@qiuwenhuifx
Copy link

qiuwenhuifx commented Aug 24, 2023

pgsql@n97-16-026:~$ pg_probackup -V
pg_probackup 2.5.12 (PostgreSQL 15.4)
pgsql@n97-16-026:~$

INFO: Backup files are synced, time elapsed: 0
INFO: Validating backup RZW6OO
ERROR: Cannot seek block 261889 of "/data00/pgsql/backup/backups/pg_5436/RZW6OO/database/base/16393/16440.1": Invalid argument
ERROR: Data files validation failed
pgsql@n97-16-066:$ du -sh /data00/pgsql/backup/backups/pg_5436/RZW6OO/database/base/16393/16440.1
2.4G /data00/pgsql/backup/backups/pg_5436/RZW6OO/database/base/16393/16440.1
pgsql@n97-16-066:$

I see there is a pull patch to fix this bug:(https://github.com/postgrespro/pg_probackup/pull/510),What is a very robust reason not to fix this bug
@jianyang1982
Copy link

I also meet this bug ,use 2.5.12, my one datafile is large then 9GB,backup failed. so sad,please fix it as soon as possible.
info bellow :
[postgres@pgmaster2 ~]$ pg_probackup --version
pg_probackup 2.5.12 (PostgreSQL 9.6.24)

ERROR: Cannot seek block 800240 of "/paic/pgbackup/mhisdrgs/pgrman/backups/mhisdrgs/S1JPEW/database/base/16411/17093": Invalid argument
ERROR: Data files validation failed

@fukanchik
Copy link

We do not have access to a postgres with 2GB segments. Your patches are welcome!

@jianyang1982
Copy link

my postgresql version is 9.6.2 ,pg_probackup complie it with error ‘connect.h’,so i use 9.6.24 complied it instead。when I complie posgresql 9.6.2 ,I use --with-segsize=10 ,so the largest file is 10GB. You can use this parameter,and file data file large than that,maybe can repeat this bug。Thank you。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants