That doesn't answer where it can be purchased, nor does it imply that it will be available for purchase when all translations are complete. At 167 pages, part 1 could conceivably be it's own book for purchase. I too would love a resource like this as a book and would be willing to pay for it. I would even purchase each part individually as they become available.
I think the book is free because Egor and PostgresPro want to develop the community. If you want to pay back - you can just start contributing to Postgres. No need to wait :)
I would love to know where to send bugs (a convenient place may be a repo in their GH org (https://github.com/postgrespro), to potentially avoid duplicate reports)
As this book's translator, I'm really excited to see the interest it triggers. Thank you for willing to help!
I'll nudge our team about an open mirror, but meanwhile you can contact us at edu@postgrespro.ru.
Bug reports on what's already out there will be very helpful to further improve both this part and what is yet to come.
There seems to be a demand for developers who know the internals of Postgres to evolve and customize it given that it is being used, at different levels of abstraction/layers, by basically all cloud providers (AWS, MS, Google, etc) and by some DB SaaS. BTW, that would be a cool job to have...
Another recent one, AlloyDB from Google Cloud. Looks pretty interesting/promising. Sort of like their competitor to AWS Aurora, built on top of Postgres, with the added ability to handle OLAP workloads well (along with apparently great OLTP performance).
TimescaleDB and Citus are notable too.
But yeah, if you’re building a DB product, starting with Postgres and customizing from there seems like an excellent approach.
Most of the changes aren’t relevant to upstream - a lot these companies seem to be using Postgres as a frontend over some kind of secret sauce, usually related to custom storage or deployments or the like. Postgres seems very modular and pluggable that way.
I assume for the common Postgres core changes everyone is already incentivised to contribute changes back upstream - the companies are banking on Postgres popularity can need it to have an excellent reputation even outside of their specific customised offering.
Timescale is hiring for a Software Engineer (Database Internals) and this could also be a senior-level hire. It's based on PostgreSQL but if the rest of the resume stacks up it's not 100% essential that you've worked on PostgreSQL internals before. Global, remote.
This series of deep articles about Postgres index types looks like it's by the same authors, and is one of the few sources I've found that really goes into the data structures used:
> If you want to use any part of this document and/or any figure, please contact me. If you work at Amazon, you cannot use and refer to this document because of the copyright violation issues.
This is an interesting inclusion, would they be referring to copies of this book being sold on Amazon? Or usage in their documentation? I'm genuinely curious what the issue is with them...
Unlikely, Postgres license is as liberal as they get:
> Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.
35 comments
[ 4.2 ms ] story [ 86.1 ms ] threadlinked from their own website: https://postgrespro.ru/education/books/internals
I would love to know where to send bugs (a convenient place may be a repo in their GH org (https://github.com/postgrespro), to potentially avoid duplicate reports)
I'll nudge our team about an open mirror, but meanwhile you can contact us at edu@postgrespro.ru. Bug reports on what's already out there will be very helpful to further improve both this part and what is yet to come.
TimescaleDB and Citus are notable too.
But yeah, if you’re building a DB product, starting with Postgres and customizing from there seems like an excellent approach.
Great to see these sorts of things, Postgres has been amazing and glad people realise it.
I assume for the common Postgres core changes everyone is already incentivised to contribute changes back upstream - the companies are banking on Postgres popularity can need it to have an excellent reputation even outside of their specific customised offering.
What would be an ideal resume for someone who never worked on Postgres
This series of deep articles about Postgres index types looks like it's by the same authors, and is one of the few sources I've found that really goes into the data structures used:
https://habr.com/en/company/postgrespro/blog/441962/
I expect those articles will turn into chapters in this book.
This is an interesting inclusion, would they be referring to copies of this book being sold on Amazon? Or usage in their documentation? I'm genuinely curious what the issue is with them...
> Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.
https://www.postgresql.org/about/licence/
Are there resources of similar quality available for MySQL / MariaDB internals ?