<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/6fb372b9f09d41b59692cf4de44441d8&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/6fb372b9f09d41b59692cf4de44441d8-1715635960965.gif</thumbnail_url><duration>580.7</duration><title>PostgreSQL physical replication with Docker containers</title><description>RailsConf 2024 Workshop Follow-up: Enabling physical replication

- After running pg_basebackup, run &quot;docker start&quot; on the exited/killed container, and make sure it starts up using the newly replaced data directory
- Compare the system identifiers between db01 and db02, they should be the same
- Ensure db01 can be reached using the &quot;replication_user&quot; user from db02, by connecting to the &quot;postgres&quot; database</description></oembed>