<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pgrx on Yonk-Labs</title><link>https://yonk.dev/tags/pgrx/</link><description>Recent content in Pgrx on Yonk-Labs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Yonk-Labs</copyright><lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yonk.dev/tags/pgrx/index.xml" rel="self" type="application/rss+xml"/><item><title>I made pg-raggraph 7× faster by deleting code I wrote. Here's where it goes next.</title><link>https://yonk.dev/blog/pg-raggraph-where-it-could-go-rust-extension-perf/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://yonk.dev/blog/pg-raggraph-where-it-could-go-rust-extension-perf/</guid><description>A 17× perf gap between pg-raggraph and Apache AGE turned out to be 5 lines of glue code in the bakeoff adapter, not an architectural problem. The fix, the four library-side wins still on the floor, and the three architectural directions ahead — pg_net sidecar, pgrx Rust extension, hybrid embedding tiers.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://yonk.dev/blog/pg-raggraph-where-it-could-go-rust-extension-perf/feature.jpg"/></item></channel></rss>