<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data-Federation on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/data-federation/</link>
    <description>Recent content in Data-Federation on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/data-federation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted PostgreSQL Data Federation: postgres_fdw vs mysql_fdw vs tds_fdw — Cross-Database Query Guide</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-postgresql-fdw-data-federation-postgres-fdw-mysql-fdw-tds-fdw-guide/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-postgresql-fdw-data-federation-postgres-fdw-mysql-fdw-tds-fdw-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Modern self-hosted architectures rarely rely on a single database engine. A typical deployment might use PostgreSQL for transactional data, MySQL for a legacy application, and Microsoft SQL Server for a vendor system. PostgreSQL&amp;rsquo;s Foreign Data Wrapper (FDW) framework enables transparent cross-database queries — you can &lt;code&gt;JOIN&lt;/code&gt; a local PostgreSQL table with a remote MySQL table in a single SQL statement without ETL pipelines.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
