News for hackers. Stuff that matters.
Re:The Internals of PostgreSQL by collegeburner on Thursday February 17, 2022 @12:21PM (#30375850)
Maybe to do with amazon implementing postgres compatibility in aurora? Reading this could leave an argument that it's not a "clean-room" implementation and is a license violation.
Re:The Internals of PostgreSQL by paulryanrogers on Thursday February 17, 2022 @01:51PM (#30377026)
Pg's license is like BSD/MIT. So long as they provide attribution why would they bother trying to do a clean room reimplementation?
Re:The Internals of PostgreSQL by alberth on Thursday February 17, 2022 @02:37PM (#30377628)
You might be confusing what a license agreement is vs what copyright assignment is.
Re:The Internals of PostgreSQL by detaro on Thursday February 17, 2022 @02:39PM (#30377648)
doesn't sound like it.
Re:The Internals of PostgreSQL by jtc331 on Thursday February 17, 2022 @01:59PM (#30377124)
Aurora isn’t a reimplementation anyway, it’s a fork with the storage layer replaced.
Re:The Internals of PostgreSQL by dikei on Thursday February 17, 2022 @08:47PM (#30381234)
Depending on the database, changing the storage layer might require changing almost everything: the query planner, optimizer and executioner intrinsically need to know how storage works to make queries efficient.
Re:The Internals of PostgreSQL by jtc331 on Friday February 25, 2022 @07:48AM (#30466697)
Aurora most definitely does not do that for Postgres. Postgres’s storage layer is separate enough that this is quite possible.

Edit: maybe the confusion here is about what “storage layer” means here. The physical row encoding is still the same. What’s different in Aurora (there are white papers on this) is how the WAL records get applied directly to encoding aware distributed as opposed to separately syncing the heap storage to disk.