<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on Gabe Fierro</title><link>https://gtf.fyi/posts/tools/</link><description>Recent content in Tools on Gabe Fierro</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 03 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gtf.fyi/posts/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Temporary Postgres Databases</title><link>https://gtf.fyi/posts/tools/pg/</link><pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate><guid>https://gtf.fyi/posts/tools/pg/</guid><description>&lt;p>When teaching my undergraduate database course, I often have the need for writing little &amp;ldquo;throwaway&amp;rdquo; SQL tables and queries to help illustrate concepts or to test out a feature. Connecting to the &amp;ldquo;real&amp;rdquo; course server
is inconvenient for a number of reasons: there is too much friction with my password manager to get the right login for the database, I have to make sure I&amp;rsquo;m on the right WiFi network (thanks to new IT policies), and I&amp;rsquo;d like to be able to demonstrate queries/actions that may cause problems for the course server without worrying about breaking anything.&lt;/p></description></item></channel></rss>