Skip to content

Blogpost on pgBackRest being Back #1187

Merged
edithturn merged 11 commits into
percona:mainfrom
janwieremjewicz:pgBackRestBack
May 21, 2026
Merged

Blogpost on pgBackRest being Back #1187
edithturn merged 11 commits into
percona:mainfrom
janwieremjewicz:pgBackRestBack

Conversation

@janwieremjewicz
Copy link
Copy Markdown
Collaborator

adding a blogpost with Community perspective on how the things have rolled out.

@janwieremjewicz
Copy link
Copy Markdown
Collaborator Author

2026-05-19_14-58-56.pdf
For those who do not want to run Hugo

- blog/2026/05/Jan-pgb-back-cover.png
---

The crisis unfolded over the course of a couple of weeks since 27 April, 2026 and the [announcement](https://pgbackrest.org/news.html):
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't start hugo locally, but will this type of start look good on the index page?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the pdf attached in the msg above. IMHO it looks ok. Added here as well..
Uploading 2026-05-19_14-58-56.pdf…

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be fixed now


This is the “[Nebraska guy problem](https://xkcd.com/2347/)” in action: software used by a large part of the industry, sustained by a very small number of people.

Yes, [anyone can fork the project](https://github.com/pgbunker/pgbunker), but:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to single out one fork? there are multiple

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my PoV this was the first one but good catch.. TBH it makes sense not to. I will update!


and

> how do we name our fork?
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be "what do we name our fork?" rather than "how", right?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done


The short version:

- **Percona** has [coordinated with multiple companies](https://pgbackrest.org/news.html#will-continue) to [secure funding for the original maintainer](https://www.globenewswire.com/news-release/2026/05/19/3297383/0/en/open-source-stays-open-percona-sponsors-pgbackrest-to-keep-postgresql-backups-running.html)
Copy link
Copy Markdown

@AndersAstrand AndersAstrand May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to make Percona seem like the main hero here? It can feel a bit self serving for a reader. Maybe focus on the coalition of companies as a whole?

I would personally stop reading here if I wasn't at percona. But I might not be the target audience :)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I specifically link the message from David and mention that we have coordinated with multiple companies. On the other hand, while this is not a race, I also want to show what else do we do...

But I get your PoV. It makes sense that it may be taken as stealing the light from others... Reworked it!

@edithturn edithturn merged commit 05d9824 into percona:main May 21, 2026
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

Successfully merging this pull request may close these issues.

4 participants