Hacker News: malisper

New comment by malisper in "Claude Fable 5.1"

malisper — Tue, 01 Sep 2026 18:13:31 +0000

Most of the work I've done with pgrust hasn't had issues with Fable. The only time I've had issues is when building a fuzz tester to find bugs

New comment by malisper in "JIT Compiling Code in 5μs"

malisper — Sun, 23 Aug 2026 14:23:41 +0000

Eval would count as JIT compilation though[0]

[0] https://www.sbcl.org/manual/#compiler-only-implementation

New comment by malisper in "JIT Compiling Code in 5μs"

malisper — Sun, 23 Aug 2026 14:12:02 +0000

Author here. Let me know if you have any questions about the post or about pgrust.

New comment by malisper in "JIT Compiling Code in 5μs"

malisper — Sun, 23 Aug 2026 14:11:27 +0000

> There's no rarity of JITs, it's just that LLVM (and other frameworks) are often used

Except that using LLVM has high latency limitting it's applicability. Postgres just disabled LLVM by default because of this[0].

[0] https://www.postgresql.org/message-id/E1w8GWU-002bSL-31%40ge...

New comment by malisper in "There's no reason for software to be slow anymore"

malisper — Sat, 22 Aug 2026 05:58:17 +0000

> This person doesn't understand how to make efficient code

The author is one of the most knowledgeable people about performance there is

JIT Compiling Code in 5μs

malisper — Thu, 20 Aug 2026 14:51:53 +0000

Article URL: https://malisper.me/jit-compiling-code-in-5-us/

Comments URL: https://news.ycombinator.com/item?id=49375459

Points: 3

# Comments: 0

New comment by malisper in "A decades-old bug in Knuth's long division (TAOCP Vol II, Algorithm 4.3.1D)"

malisper — Wed, 19 Aug 2026 13:18:23 +0000

You still get a physical piece of paper that looks like a check; it's just not a valid check.

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sun, 09 Aug 2026 01:36:53 +0000

We've fixed the issue on our development branch. We've only been working with the default collation so when you try a different one it causes an issue

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 12:08:43 +0000

How so? Window functions work exactly the same way. Postgres processes them one row at a time, and you can batch them the same way as you would with sum.

Window functions do make parallel queries more difficult, but that's a different story.

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 12:06:53 +0000

> You’re cosplaying as someone who could build a database.

> In reality you yourself could never build Postgres or Redis or any other database.

> You’re not skilled enough or knowledgeable enough and you’re not willing to put the time in so you’ve simple vibe copied Postgres.

What makes you think these things? I've been writing about the Postgres internals and giving talks about Postgres for a decade and have managed a Postgres cluster as big as 1PB of data

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 12:01:22 +0000

Can you file an issue? We know there are bugs and the work we're doing with formal verification and fuzz testing is to go through all the code and make sure all of it behaves identically to Postgres

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 11:56:18 +0000

We don't expose the priorities right now, but we have the priorities decay over time. That way faster queries get prioritized over long running queries. That should achieve the behavior you're looking for.

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 11:20:17 +0000

Can you file an issue? Our big focus over the next few weeks is to eliminate these issues and that's why we're our formal verification and fuzz testing work

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 04:36:54 +0000

Yes. Email me and Jason at malis@pgrust.com and jason@pgrust.com

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 03:32:02 +0000

I'm certain pgrust can find a long term home somewhere

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 01:15:35 +0000

Thanks!

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Sat, 08 Aug 2026 00:42:39 +0000

What do you mean by native TTL? Would that be when rows are automatically deleted if they aren't touched after a certain period of time?

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Fri, 07 Aug 2026 23:10:16 +0000

^For context, this is Greg Smith, the author of Postgres 9.0 High Performance[0]. That book was my first introduction to Postgres

[0] https://www.amazon.com/dp/184951030X

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Fri, 07 Aug 2026 23:04:16 +0000

> My understanding is that they used c2rust, and then told the LLM/Agents to make the code more idiomatic rust, while also using the PG test suite as a feedback mechanism.

This is correct

> and thus a fork, and should thus have the original license and copyright preserved)

This is not correct. The Postgres license is permissive. We need to include a copy of the license (which we do in the NOTICE file[0]) but we CAN relicense the Postgres code however we want as long as we meet the requirements of the license. pgrust is a derived work of Postgres, but Postgres allows derived works to be under a different license.

[0] https://github.com/malisper/pgrust/blob/main/NOTICE

New comment by malisper in "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"

malisper — Fri, 07 Aug 2026 22:56:38 +0000

It absolutely can be embedded. The bigger enabler is replacing the process-per-connection model with a thread-per-connection model. Projects like pglite[0] had to give up concurrency because of it. We also support compiling to wasm so you can embed it in the browser too, which is what powers pgrust.com

[0] https://github.com/electric-sql/pglite

[1] https://pgrust.com/