Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Commentary says pgrust testing uncovered PostgreSQL bugs

AI summary

A commentary on Michael Malis’s pgrust project says its testing uncovered several PostgreSQL defects: a numerical issue that can cause valid SP-GiST operations to fail, a format-cache issue that can produce incorrect JSONPath results, a pgcrypto issue that can cause later operations to fail, multiple memory-safety issues in the dictionary loader, and an overflow issue. The commentator says pgrust is not bug-free but involves substantial testing, and that its primary pitch is performance optimization.

In-depth insight

The commentary links extensive testing of pgrust to the reported discovery of concrete PostgreSQL bugs, providing a documented example of testing outside PostgreSQL’s core development identifying database defects.

“We should be more ambitious with the software we build”

Since early this year, Michael Malis (of pgrust) has been showing me interesting things he's done and saying

[W]e should be more ambitious1 with the software we build

There is, understandably, a lot of skepticism about projects like pgrust because there are so many low-quality AI-generated projects out there. If I didn't know Malis and didn't look into it, I would just assume that pgrust was another vibe slopped project that's never going to work. But I know Malis well enough to trust his work without looking into it, and if you look into it a bit, you'll see that in testing pgrust, he's testing thoroughly enough that he's even uncovering real bugs in Postgres, such as this numerical bug that can cause valid SP-GiST operations to fail, this format cache bug that can cause incorrect results from JSONPath, this pgcrypto bug that can cause later operations to fail, multiple memory safety bugs in the dictionary loader2, this money overflow bug, etc.

This isn't to say that pgrust is bug free3, but it does indicate that there's a substantial amount of testing happening and, even if pgrust itself is never successful, just making the attempt will have improved Postgres in a durable way. The main pitch for pgrust is actually performance, and that's where the really interesting work is happening; if pgrust fails, it's possible that some of the optimizations they've demonstrated will make it into Postgres, Clickhouse, etc., but that's obviously less direct than filing Postgres bugs which get fixed.

#pgrust#PostgreSQL#Michael Malis#pgcrypto#SP-GiST#JSONPath

Original · 31 min readRead the original
Group chat

No comments yet. Start the conversation.