<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Migration on PIGSTY</title>
    <link>https://v27.pgsty.pro/tags/migration/</link>
    <description>Recent content in Migration on PIGSTY</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate>
    
    
      <atom:link href="https://v27.pgsty.pro/tags/migration/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Migration</title>
        <link>https://v27.pgsty.pro/docs/pgsql/migration/</link>
        <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
        
        <guid>https://v27.pgsty.pro/docs/pgsql/migration/</guid>
        <description>&lt;p&gt;Pigsty has a built-in playbook &lt;a href=&#34;https://github.com/Vonng/pigsty/blob/v2.7.0/pgsql-migration.yml&#34;&gt;&lt;code&gt;pgsql-migration.yml&lt;/code&gt;&lt;/a&gt; to perform online database migration based on logical replication.&lt;/p&gt;&#xA;&lt;p&gt;With proper automation, the downtime could be minimized to several seconds. But beware that logical replication requires PostgreSQL 10+ to work. You can still use the facility here and use a pg_dump | psql instead of logical replication.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;define-a-migration-task&#34;&gt;Define a Migration Task&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;You have to create a migration task definition file to use this playbook.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
