<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>RustProof Labs blog recent posts</title><link>https://blog.rustprooflabs.com/rss/recent</link><description>RustProof Labs: blogging for knowledge is a technical blog focused on PostgreSQL, data, and other technical interests.</description><language>en-US</language><copyright>© RustProof Labs</copyright><lastBuildDate>Wed, 18 Mar 2026 13:11:38 GMT</lastBuildDate><generator>rfeed v1.1.1</generator><docs>https://github.com/svpino/rfeed/blob/master/README.md</docs><item><title>Improved Quality in OpenStreetMap Road Network for pgRouting</title><link>https://blog.rustprooflabs.com/2025/12/pgosm-flex-pgrouting-performance-quality-improvements</link><description>&lt;p&gt;Recent changes in the software bundled in &lt;a href="https://pgosm-flex.com/"&gt;PgOSM Flex&lt;/a&gt;
resulted in unexpected improvements when using OpenStreetMap roads data for routing.
The short story: routing with PgOSM Flex 1.2.0 is faster, easier, and
produces higher quality data for routing! I came to this conclusion after completing a
variety of testing with the old and new versions of PgOSM Flex. This post outlines
my testing and findings.&lt;/p&gt;
&lt;p&gt;The concern I had before this testing was that the variety of changes involved in preparing
data for routing in PgOSM Flex 1.2.0 might have degraded routing quality.
I am beyond thrilled with what I found instead. Quality of the generated
network didn't suffer at all, it was a major win!&lt;/p&gt;
&lt;h2&gt;What Changed?&lt;/h2&gt;
&lt;p&gt;The changes started with
&lt;a href="https://github.com/rustprooflabs/pgosm-flex/releases/tag/1.1.1"&gt;PgOSM Flex 1.1.1&lt;/a&gt;
by bumping internal versions used in PgOSM Flex to Postgres 18, PostGIS 3.6, osm2pgsql 2.2.0,
and Debian 13. There was not expected to be any significant changes bundled in that release.
After v1.1.1 was released, it came to my attention that
&lt;a href="https://github.com/pgRouting/pgrouting/releases/tag/v4.0.0"&gt;pgRouting 4.0 had been released&lt;/a&gt;
and that update broke the &lt;a href="https://pgosm-flex.com/routing.html"&gt;routing instructions&lt;/a&gt;
in PgOSM Flex's documentation. This was thankfully
&lt;a href="https://github.com/rustprooflabs/pgosm-flex/issues/408"&gt;reported by Travis Hathaway&lt;/a&gt;
who also helped verify the updates to the process.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;pgRouting 4 removed the &lt;code&gt;pgr_nodeNetwork&lt;/code&gt;, &lt;code&gt;pgr_createTopology&lt;/code&gt;, and &lt;code&gt;pgr_analyzeGraph&lt;/code&gt; functions.
Removing these functions was the catalyst for the changes made in PgOSM Flex 1.2.0.
I had used those &lt;code&gt;pgr_*&lt;/code&gt; functions as part of my core process in data preparation for routing
for as long as I have used pgRouting.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;After &lt;a href="https://github.com/rustprooflabs/pgosm-flex/pull/411"&gt;adjusting the documentation&lt;/a&gt;
it became clear there were
&lt;a href="https://github.com/rustprooflabs/pgosm-flex/issues/408#issuecomment-3675676507"&gt;performance issues&lt;/a&gt; using the replacement functions in pgRouting 4.0, namely in &lt;code&gt;pgr_separateTouching()&lt;/code&gt;.
The performance issue in the pgRouting function is reported as &lt;a href="https://github.com/pgRouting/pgrouting/issues/3010"&gt;pgrouting#3010&lt;/a&gt;.
Working through the performance challenges resulted in
&lt;a href="https://github.com/rustprooflabs/pgosm-flex/releases/tag/1.1.2"&gt;PgOSM Flex 1.1.2&lt;/a&gt;
and ultimately &lt;a href="https://github.com/rustprooflabs/pgosm-flex/releases/tag/1.2.0"&gt;PgOSM Flex 1.2.0&lt;/a&gt;
that now uses a custom procedure to prepare the edge network far better suited
to OpenStreetMap data.&lt;/p&gt;
</description><pubDate>Sun, 28 Dec 2025 05:01:00 GMT</pubDate><guid isPermaLink="true">https://blog.rustprooflabs.com/2025/12/pgosm-flex-pgrouting-performance-quality-improvements</guid></item><item><title>Local LLM with OpenWeb UI and Ollama</title><link>https://blog.rustprooflabs.com/2026/03/local-llm-openweb-ui-ollama</link><description>&lt;p&gt;Like much of the world, I have been exploring capabilities and realities of LLMs and other
generative tools for a while now. I am focused on using the
technology with the framing of my technology-focused work, plus my other common scoping
on data privacy and ethics. I want basic
coding help (SQL, Python, Docker, PowerShell, DAX), ideation, writing boilerplate code,
and leveraging existing procedures. Naturally, I want this available offline
in a private and secure environment. I have been focused on running a local LLM with
&lt;a href="https://en.wikipedia.org/wiki/Retrieval-augmented_generation"&gt;RAG capabilities&lt;/a&gt;
and having control over what data goes where, and how it is used.
Especially data about my conversations with the generative LLM.&lt;/p&gt;
&lt;p&gt;This post collects my notes on what my expectations and goals are, and outlines the components
I am using currently, and thoughts on my path forward.&lt;/p&gt;
</description><pubDate>Wed, 18 Mar 2026 05:01:00 GMT</pubDate><guid isPermaLink="true">https://blog.rustprooflabs.com/2026/03/local-llm-openweb-ui-ollama</guid></item></channel></rss>