{"id":43239,"date":"2026-02-27T11:51:38","date_gmt":"2026-02-27T10:51:38","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=43239"},"modified":"2026-02-27T11:51:41","modified_gmt":"2026-02-27T10:51:41","slug":"postgresql-19-pg_dumpall-in-binary-format","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/","title":{"rendered":"PostgreSQL 19: pg_dumpall in binary format"},"content":{"rendered":"\n<p>One of the limitation of <a href=\"https:\/\/www.postgresql.org\/docs\/18\/app-pg-dumpall.html\" target=\"_blank\" rel=\"noreferrer noopener\">pg_dumpall<\/a> up to PostgreSQL version 18 is, that you can only dump in text mode. While <a href=\"https:\/\/www.postgresql.org\/docs\/18\/app-pgdump.html\" target=\"_blank\" rel=\"noreferrer noopener\">pg_dump<\/a> can dump in various formats (plain,custom,tar and directory) since ages. pg_dump was always limited to text mode. This will change with PostgreSQL 19 because <a href=\"https:\/\/git.postgresql.org\/gitweb\/?p=postgresql.git;a=commitdiff;h=763aaa06f03401584d07db71256fc0ab47235cce\" target=\"_blank\" rel=\"noreferrer noopener\">this was committed recently<\/a>.<\/p>\n\n\n\n<p>The default is still plain text but now you have the same options as pg_dump:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_dumpall --help | grep -A 1 -w format\n  -F, --format=c|d|t|p         output file format (custom, directory, tar,\n                               plain text (default))\n<\/pre><\/div>\n\n\n<p>Lets assume we have have five user databases like this:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,2]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] for i in {1..5}; do createdb ${i}; done\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -l\n                                                        List of databases\n   Name    |  Owner   | Encoding | Locale Provider |   Collate   |    Ctype    |   Locale    | ICU Rules |   Access privileges   \n-----------+----------+----------+-----------------+-------------+-------------+-------------+-----------+-----------------------\n 1         | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | \n 2         | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | \n 3         | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | \n 4         | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | \n 5         | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | \n postgres  | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | \n template0 | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | =c\/postgres          +\n           |          |          |                 |             |             |             |           | postgres=CTc\/postgres\n template1 | postgres | UTF8     | icu             | en_US.UTF-8 | en_US.UTF-8 | en-US-x-icu |           | =c\/postgres          +\n           |          |          |                 |             |             |             |           | postgres=CTc\/postgre\n<\/pre><\/div>\n\n\n<p>&#8230; and a table in each:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] for i in {1..5}; do psql -c &quot;create table t${i} as select * from generate_series(1,100)&quot; ${i}; done\nSELECT 100\nSELECT 100\nSELECT 100\nSELECT 100\nSELECT 100\n<\/pre><\/div>\n\n\n<p>Dumping that using the default mode of pg_dumpall results in a plain text as usual:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_dumpall &amp;gt; dmp.sql\npostgres@:\/home\/postgres\/ &#x5B;pgdev] head -50 dmp.sql | egrep -v &quot;^$&quot;\npostgres@:\/home\/postgres\/ &#x5B;pgdev] head -50 dmp.sql | egrep -v &quot;^$|--&quot;\n\\restrict fkHQ08xl5cQnk99WM6prphaZBPdqlARNru7uAdgFRFMUJm7RdeI6Elk8zoOr8mg\nSET default_transaction_read_only = off;\nSET client_encoding = &#039;UTF8&#039;;\nSET standard_conforming_strings = on;\nCREATE ROLE postgres;\nALTER ROLE postgres WITH SUPERUSER INHERIT CREATEROLE CREATEDB LOGIN REPLICATION BYPASSRLS;\n\\unrestrict fkHQ08xl5cQnk99WM6prphaZBPdqlARNru7uAdgFRFMUJm7RdeI6Elk8zoOr8mg\n\\connect template1\n\\restrict EFrJ3U9GH8T5SSHUVhWam0FHhJyxp1pAMXSTXTLVaiHayK4ASUZzweTUywMJbmq\n<\/pre><\/div>\n\n\n<p>Starting with PostgreSQL 19 this can be changed to any of the other supported formats. The tar format will give you a directory structure like this:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,2,9]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_dumpall --format=t -f dmp_tar\npostgres@:\/home\/postgres\/ &#x5B;pgdev] ls -la dmp_tar\/\ntotal 12\ndrwx------. 1 postgres postgres   46 Feb 27 08:53 .\ndrwx------. 1 postgres postgres  436 Feb 27 08:53 ..\ndrwx------. 1 postgres postgres  110 Feb 27 08:53 databases\n-rw-r--r--. 1 postgres postgres  448 Feb 27 08:53 map.dat\n-rw-r--r--. 1 postgres postgres 1810 Feb 27 08:53 toc.glo\npostgres@:\/home\/postgres\/ &#x5B;pgdev] ls -la dmp_tar\/databases\/\ntotal 56\ndrwx------. 1 postgres postgres  110 Feb 27 08:53 .\ndrwx------. 1 postgres postgres   46 Feb 27 08:53 ..\n-rw-r--r--. 1 postgres postgres 6656 Feb 27 08:53 16388.tar\n-rw-r--r--. 1 postgres postgres 6656 Feb 27 08:53 16389.tar\n-rw-r--r--. 1 postgres postgres 6656 Feb 27 08:53 16390.tar\n-rw-r--r--. 1 postgres postgres 6656 Feb 27 08:53 16391.tar\n-rw-r--r--. 1 postgres postgres 6656 Feb 27 08:53 16392.tar\n-rw-r--r--. 1 postgres postgres 6656 Feb 27 08:53 1.tar\n-rw-r--r--. 1 postgres postgres 5632 Feb 27 08:53 5.tar\n<\/pre><\/div>\n\n\n<p>The &#8220;map&#8221; file maps OIDs to database names:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] cat dmp_tar\/map.dat \n#################################################################\n# map.dat\n#\n# This file maps oids to database names\n#\n# pg_restore will restore all the databases listed here, unless\n# otherwise excluded. You can also inhibit restoration of a\n# database by removing the line or commenting out the line with# a # mark.\n#################################################################\n1 template1\n16388 1\n16389 2\n16390 3\n16391 4\n16392 5\n5 postgres\n<\/pre><\/div>\n\n\n<p>The &#8220;toc&#8221; file, as usual is the table of contents which can be listed with <a href=\"https:\/\/www.postgresql.org\/docs\/18\/app-pgrestore.html\" target=\"_blank\" rel=\"noreferrer noopener\">pg_restore<\/a>:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_restore -l dmp_tar\/toc.glo\n;\n; Archive created at 2026-02-27 08:53:53 CET\n;     dbname: postgres\n;     TOC Entries: 10\n;     Compression: none\n;     Dump Version: 1.16-0\n;     Format: CUSTOM\n;     Integer: 4 bytes\n;     Offset: 8 bytes\n;     Dumped by pg_dump version: 19devel dbi services build\n;\n;\n; Selected TOC Entries:\n;\n1; 0 0 default_transaction_read_only - default_transaction_read_only \n2; 0 0 client_encoding - client_encoding \n3; 0 0 standard_conforming_strings - standard_conforming_strings \n4; 0 0 DROP_GLOBAL - DATABASE &quot;1&quot; \n5; 0 0 DROP_GLOBAL - DATABASE &quot;2&quot; \n6; 0 0 DROP_GLOBAL - DATABASE &quot;3&quot; \n7; 0 0 DROP_GLOBAL - DATABASE &quot;4&quot; \n8; 0 0 DROP_GLOBAL - DATABASE &quot;5&quot; \n9; 0 0 DROP_GLOBAL - ROLE postgres \n10; 0 0 ROLE - ROLE postgres \n<\/pre><\/div>\n\n\n<p>This comes with the possibility (as with the plain text format) to restore individual databases out of this global dump, or to reload global object only:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,16]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_restore --globals-only dmp_tar\/ -d postgres --verbosepg_restore: connecting to database for restore\npg_restore: executing SELECT pg_catalog.set_config(&#039;search_path&#039;, &#039;&#039;, false);\npg_restore: creating default_transaction_read_only &quot;default_transaction_read_only&quot;\npg_restore: creating client_encoding &quot;client_encoding&quot;\npg_restore: creating standard_conforming_strings &quot;standard_conforming_strings&quot;\npg_restore: creating ROLE &quot;ROLE postgres&quot;\npg_restore: while PROCESSING TOC:\npg_restore: from TOC entry 10; 0 0 ROLE ROLE postgres (no owner)\npg_restore: error: could not execute query: ERROR:  role &quot;postgres&quot; already exists\nCommand was: CREATE ROLE postgres;\nALTER ROLE postgres WITH SUPERUSER INHERIT CREATEROLE CREATEDB LOGIN REPLICATION BYPASSRLS;\n\npg_restore: database restoring skipped because option -g\/--globals-only was specified\npg_restore: warning: errors ignored on restore: 1\n\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_restore --globals-only dmp_tar\/ -d postgres --verbosepg_restore: connecting to database for restore\npg_restore: executing SELECT pg_catalog.set_config(&#039;search_path&#039;, &#039;&#039;, false);\npg_restore: creating default_transaction_read_only &quot;default_transaction_read_only&quot;\npg_restore: creating client_encoding &quot;client_encoding&quot;\npg_restore: creating standard_conforming_strings &quot;standard_conforming_strings&quot;\npg_restore: creating ROLE &quot;ROLE postgres&quot;\npg_restore: while PROCESSING TOC:\npg_restore: from TOC entry 10; 0 0 ROLE ROLE postgres (no owner)\npg_restore: error: could not execute query: ERROR:  role &quot;postgres&quot; already exists\nCommand was: CREATE ROLE postgres;\nALTER ROLE postgres WITH SUPERUSER INHERIT CREATEROLE CREATEDB LOGIN REPLICATION BYPASSRLS;\n\npg_restore: database restoring skipped because option -g\/--globals-only was specified\npg_restore: warning: errors ignored on restore: 1\n<\/pre><\/div>\n\n\n<p>Another option is to run multiple restore processes to load databases in parallel. Nice to have that option and as usual: Thanks to all involved.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the limitation of pg_dumpall up to PostgreSQL version 18 is, that you can only dump in text mode. While pg_dump can dump in various formats (plain,custom,tar and directory) since ages. pg_dump was always limited to text mode. This will change with PostgreSQL 19 because this was committed recently. The default is still plain [&hellip;]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[77],"type_dbi":[],"class_list":["post-43239","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-postgresql"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>PostgreSQL 19: pg_dumpall in binary format - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 19: pg_dumpall in binary format\" \/>\n<meta property=\"og:description\" content=\"One of the limitation of pg_dumpall up to PostgreSQL version 18 is, that you can only dump in text mode. While pg_dump can dump in various formats (plain,custom,tar and directory) since ages. pg_dump was always limited to text mode. This will change with PostgreSQL 19 because this was committed recently. The default is still plain [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-27T10:51:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-02-27T10:51:41+00:00\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"PostgreSQL 19: pg_dumpall in binary format\",\"datePublished\":\"2026-02-27T10:51:38+00:00\",\"dateModified\":\"2026-02-27T10:51:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/\"},\"wordCount\":207,\"commentCount\":0,\"keywords\":[\"PostgreSQL\"],\"articleSection\":[\"Database Administration &amp; Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/\",\"name\":\"PostgreSQL 19: pg_dumpall in binary format - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2026-02-27T10:51:38+00:00\",\"dateModified\":\"2026-02-27T10:51:41+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 19: pg_dumpall in binary format\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &amp;\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\/\/x.com\/westermanndanie\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL 19: pg_dumpall in binary format - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 19: pg_dumpall in binary format","og_description":"One of the limitation of pg_dumpall up to PostgreSQL version 18 is, that you can only dump in text mode. While pg_dump can dump in various formats (plain,custom,tar and directory) since ages. pg_dump was always limited to text mode. This will change with PostgreSQL 19 because this was committed recently. The default is still plain [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/","og_site_name":"dbi Blog","article_published_time":"2026-02-27T10:51:38+00:00","article_modified_time":"2026-02-27T10:51:41+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"PostgreSQL 19: pg_dumpall in binary format","datePublished":"2026-02-27T10:51:38+00:00","dateModified":"2026-02-27T10:51:41+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/"},"wordCount":207,"commentCount":0,"keywords":["PostgreSQL"],"articleSection":["Database Administration &amp; Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/","name":"PostgreSQL 19: pg_dumpall in binary format - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-02-27T10:51:38+00:00","dateModified":"2026-02-27T10:51:41+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-pg_dumpall-in-binary-format\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 19: pg_dumpall in binary format"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &amp;\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43239","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=43239"}],"version-history":[{"count":10,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43239\/revisions"}],"predecessor-version":[{"id":43253,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43239\/revisions\/43253"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=43239"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=43239"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=43239"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=43239"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}