3 ms·
It’s impressive that this is a single revert. That speaks to how the development of Postgres is done atomically. Also not surprised to see it was the EDB team
by boiler_up800 4y ago
It’s impressive that this is a single revert. That speaks to how the development of Postgres is done atomically.
Also not surprised to see it was the EDB team with the expertise to fix it. Their model is a little outdated but they have a lot of experts working there.
- gurjeet 4y agoI'm not sure who you're referring to as the EDB team. Please share what make you think that. The commit [1] (dug up by someone else in this discussion), references 4 people (including the committer), and only one of them seems to be EDB employee. (Info gleaned from their respective LinkedIn profiles, and from email signatures sent to pgsql-hackers list) [1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=e28bb885196916b0a3d898ae4f2be0e38108d81b https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...
- mattashii 4y agoAll of those mentioned in the commit helped in the diagnosis, while Andres was the one to detail the full chain of events that describes how the corruption happened, in [0]. [0] https://www.postgresql.org/message-id/20220524190133.j6ee7zh4f5edt5je%40alap3.anarazel.de https://www.postgresql.org/message-id/20220524190133.j6ee7zh...