<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Physical Backup on Postgres Scripts</title><link>https://www.postgresscripts.com/tags/physical-backup/</link><description>Recent content in Physical Backup on Postgres Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>PostgresScripts.com</copyright><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.postgresscripts.com/tags/physical-backup/index.xml" rel="self" type="application/rss+xml"/><item><title>PostgreSQL Physical Backup Guide with pg_basebackup</title><link>https://www.postgresscripts.com/post/postgresql-physical-backup-with-pg-basebackup/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://www.postgresscripts.com/post/postgresql-physical-backup-with-pg-basebackup/</guid><description>
&lt;h2 id="postgresql-physical-backups-with-pg_basebackup"&gt;PostgreSQL Physical Backups with pg_basebackup&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;pg_basebackup&lt;/code&gt; takes a physical, binary-level snapshot of a running PostgreSQL cluster. Unlike &lt;code&gt;pg_dump&lt;/code&gt;, which produces a logical export of one database at a time, &lt;code&gt;pg_basebackup&lt;/code&gt; captures the entire data directory — all databases, configuration files, and enough WAL to make the backup consistent. The result is suitable for two critical operations: initializing a streaming replication standby, and serving as the base for point-in-time recovery (PITR).&lt;/p&gt;</description></item></channel></rss>