Skip to content

when use pg_probackup to backup a block_size(32KB),it report error #492

Closed as not planned
@huanghy0592

Description

@huanghy0592

Hi, all:
I use the pg_probackup 2.5.5 to backup a postgresql db,it report error.It report:ERROR: block_size(32768) is not compatible(8192 expected),My postgresql is compiled the source code,
./configure --prefix=/home/postgres/postgresql-12 --with-perl --with-python --with-libxml --with-libxslt --enable-thread-safety --with-libedit-preferred --with-segsize=16 --with-blocksize=32 --with-wal-blocksize=64 --enable-nls=en_US.UTF-8
,how to solve it ?thank you.

postgres@zbx-db01_/home/postgres/postgresql-12/log
$>pg_controldata
pg_control version number: 1201
Catalog version number: 201909212
Database system identifier: 6988319331619127102
Database cluster state: in production
pg_control last modified: Wed 01 Jun 2022 02:14:27 PM CST
Latest checkpoint location: 40D04/32E476F8
Latest checkpoint's REDO location: 40D04/32BC50C8
Latest checkpoint's REDO WAL file: 0000000100040D040000000C
Latest checkpoint's TimeLineID: 1
Latest checkpoint's PrevTimeLineID: 1
Latest checkpoint's full_page_writes: on
Latest checkpoint's NextXID: 0:1498394727
Latest checkpoint's NextOID: 8008995
Latest checkpoint's NextMultiXactId: 34686
Latest checkpoint's NextMultiOffset: 88700
Latest checkpoint's oldestXID: 1321304108
Latest checkpoint's oldestXID's DB: 16386
Latest checkpoint's oldestActiveXID: 1498394726
Latest checkpoint's oldestMultiXid: 1
Latest checkpoint's oldestMulti's DB: 13468
Latest checkpoint's oldestCommitTsXid:0
Latest checkpoint's newestCommitTsXid:0
Time of latest checkpoint: Wed 01 Jun 2022 02:14:27 PM CST
Fake LSN counter for unlogged rels: 0/3E8
Minimum recovery ending location: 0/0
Min recovery ending loc's timeline: 0
Backup start location: 0/0
Backup end location: 0/0
End-of-backup record required: no
wal_level setting: replica
wal_log_hints setting: on
max_connections setting: 2000
max_worker_processes setting: 20
max_wal_senders setting: 10
max_prepared_xacts setting: 0
max_locks_per_xact setting: 64
track_commit_timestamp setting: off
Maximum data alignment: 8
Database block size: 32768
Blocks per segment of large relation: 524288
WAL block size: 65536
Bytes per WAL segment: 67108864
Maximum length of identifiers: 64
Maximum columns in an index: 32
Maximum size of a TOAST chunk: 8140
Size of a large-object chunk: 8192
Date/time type storage: 64-bit integers
Float4 argument passing: by value
Float8 argument passing: by value
Data page checksum version: 0
Mock authentication nonce: becce2e15f5172211bb26756a0579910abf00c83f6e646ec990bf4a0aabe8ae0

postgres@zbx-db01_/home/postgres/postgresql-12/log
$> pg_probackup backup -B /home/postgres/bak/ --instance local_5432 -b full -U root
INFO: Backup start, pg_probackup version: 2.5.5, instance: local_5432, backup ID: RCSC16, backup mode: FULL, wal mode: ARCHIVE, remote: false, compress-algorithm: zlib, compress-level: 5
ERROR: block_size(32768) is not compatible(8192 expected)
WARNING: Backup RCSC16 is running, setting its status to ERROR

postgres@zbx-db01_/home/postgres/postgresql-12/log
$> pg_probackup show-config -B /home/postgres/bak --instance local_5432

Backup instance information

pgdata = /home/postgres/postgresql-12/data
system-identifier = 6988319331619127102
xlog-seg-size = 67108864

Connection parameters

pgdatabase = postgres

Replica parameters

replica-timeout = 5min

Archive parameters

archive-timeout = 5min

Logging parameters

log-level-console = INFO
log-level-file = OFF
log-filename = pg_probackup.log
log-rotation-size = 0TB
log-rotation-age = 0d

Retention parameters

retention-redundancy = 0
retention-window = 3
wal-depth = 0

Compression parameters

compress-algorithm = zlib
compress-level = 5

Remote access parameters

remote-proto = ssh

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions