this post was submitted on 05 Apr 2024
19 points (100.0% liked)
PostgreSQL
665 readers
1 users here now
The world's most advanced open source relational database
Project
- About (history)
- Docs
- Donate to PostgreSQL
- Wiki
- Planet PostgreSQL
- IRC
- Mailing lists:
- pgsql-announce
- pgsql-hackers (developers)
- pgsql-general
- pgsql-jobs
- User Groups
Events
- SEAPUG Summer BBQ, 6 July in Seattle
- SFBA PostgreSQL Meetup, 12 July
- Chicago PostgreSQL Meetup, 19 July
- PGDay UK 2023, 12 September in London
- PGConf 2023, 3-5 October in New York City
- PGDay Israel 2023, 19 October
- PGConf.EU 2023, 12-15 December in Prague
Podcasts
Related Fediverse communities
- c/SQL on programming.dev
- #sql on Mastodon
- #postgresql on Mastodon
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is the best summary I could come up with:
Merged yesterday to the Git code for the PostgreSQL database server is support for facilitating incremental backups.
Robert Haas a few months ago restarted work to implement incremental backup support for PostgreSQL, years after he originally pursued the feature to no avail at that time.
But this time around things panned out and merged to PostgreSQL is support for producing incremental backups.
Haas explained in his proposal from June: The basic design of this patch set is pretty simple, and there are three main parts.
Naturally, we don't find out about blocks that were modified without any write-ahead log record, e.g. hint bit updates, but those are of necessity not critical for correctness, so it's OK. Second, pg_basebackup has a mode where it can take an incremental backup.
The PostgreSQL 17 database server stable debut is tentatively planned for next September so it will be interesting to see what other exciting changes make it for this next version.
The original article contains 524 words, the summary contains 158 words. Saved 70%. I'm a bot and I'm open source!