Re: Is it possible to add support for PostgreSQL-15 and newer versions in omnipitr?
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: "hailong.li" <hailong.li@qunar.com>
Cc: depesz@depesz.com, "xuzhao.zhao" <xuzhao.zhao@qunar.com>, pgsql-bugs@lists.postgresql.org
Date: 2023-12-13T13:33:59Z
Lists: pgsql-bugs
Greetings, * hailong.li (hailong.li@qunar.com) wrote: > OmniPITR is an very excellent software! Unfortunately, it's not been maintained in many many years and used deprecated and now removed interfaces because those interfaces resulted in cases where PG wouldn't properly restart from a crash when it should and encouraged users to do things which could lead very easily to corruption. > Btw, pgbackrest only supports the default 8k blocksize of PG instances,but > our blocksize is 32k.😭 There's been some work towards adding support for alternative block size PG instances in pgbackrest. The open pull request is here: https://github.com/pgbackrest/pgbackrest/pull/2197 If you're interested in this then I strongly encourage you to take a look at that pull request and try out pgbackrest with it and provide your feedback on it. Independently, it'd be very interesting to hear about your use case and why you're running with 32K block sizes instead of the default 8K. There's been some work to make PostgreSQL able to run with different block sizes which are chosen at initdb-time (instead of having it be a compile-time option), presumably that would also be interesting for your use-case...? Thanks, Stephen