{"id":12286,"date":"2019-03-02T22:12:41","date_gmt":"2019-03-02T21:12:41","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/"},"modified":"2023-06-15T16:32:39","modified_gmt":"2023-06-15T14:32:39","slug":"postgresql-12-new-option-exclude-database-for-pg_dumpall","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/","title":{"rendered":"PostgreSQL 12: New option –exclude-database for pg_dumpall"},"content":{"rendered":"

By Mouhamadou Diaw<\/strong><\/p>\n

Up to PostgreSQL 11 pg_dump all was used to dump all PostgreSQL databases of a cluster into one script file. The script file then contains SQL commands that can be used as input to psql to restore the databases. It does this by calling pg_dump for each database in the cluster.
\nPostgreSQL 12 is under development but we can test new features which will be implemented. Now with PostgreSQL 12 there is a new option that allows to exclude specific database with pg_dumpall. This option is called –exclude-database
\nThis option can be useful where a database name is visible but the database is not dumpable by the user.
\nWe can now see this new option in the help output<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials log]$ <\/code>\/u01\/app\/postgres\/product\/12dev\/bin\/pg_dumpall<\/code> --help | <\/code>grep<\/code> exclude<\/code><\/div>\n
--exclude-database=PATTERN\u00a0\u00a0 exclude databases whose name matches PATTERN<\/code><\/div>\n
[postgres@dbi-pg-essentials log]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

In this blog I am going to test this new option.<\/p>\n

Let\u2019s first list the databases in my cluster<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n<\/td>\n
\n
\n
postgres=# l<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>List <\/code>of<\/code> databases<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Name<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 Owner\u00a0\u00a0 | Encoding |\u00a0\u00a0 <\/code>Collate<\/code>\u00a0\u00a0 |\u00a0\u00a0\u00a0 Ctype\u00a0\u00a0\u00a0 |\u00a0\u00a0 Access <\/code>privileges<\/code><\/div>\n
-----------------+----------+----------+-------------+-------------+-----------------------<\/code><\/div>\n
\u00a0<\/code>db1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres | UTF8\u00a0\u00a0\u00a0\u00a0 | en_US.UTF-8 | en_US.UTF-8 |<\/code><\/div>\n
\u00a0<\/code>db2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres | UTF8\u00a0\u00a0\u00a0\u00a0 | en_US.UTF-8 | en_US.UTF-8 |<\/code><\/div>\n
\u00a0<\/code>mydb\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres | UTF8\u00a0\u00a0\u00a0\u00a0 | en_US.UTF-8 | en_US.UTF-8 |<\/code><\/div>\n
\u00a0<\/code>postgres\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres | UTF8\u00a0\u00a0\u00a0\u00a0 | en_US.UTF-8 | en_US.UTF-8 |<\/code><\/div>\n
\u00a0<\/code>postgres_sample | postgres | UTF8\u00a0\u00a0\u00a0\u00a0 | en_US.UTF-8 | en_US.UTF-8 |<\/code><\/div>\n
\u00a0<\/code>template0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres | UTF8\u00a0\u00a0\u00a0\u00a0 | en_US.UTF-8 | en_US.UTF-8 | =c\/postgres\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 +<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>|\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres=CTc\/postgres<\/code><\/div>\n
\u00a0<\/code>template1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres | UTF8\u00a0\u00a0\u00a0\u00a0 | en_US.UTF-8 | en_US.UTF-8 | =c\/postgres\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 +<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>|\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | postgres=CTc\/postgres<\/code><\/div>\n
(7 <\/code>rows<\/code>)<\/code><\/div>\n
<\/div>\n
postgres=#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

First let\u2019s dump all user databases<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials ~]$\u00a0 <\/code>\/u01\/app\/postgres\/product\/12dev\/bin\/pg_dumpall<\/code>\u00a0\u00a0 > with_alldb.sql\u00a0\u00a0 <\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If we do a grep in the output file, we can see that the dump contains all databases<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials ~]$ <\/code>grep<\/code> \"CREATE DATABASE\"<\/code> with_alldb.sql<\/code><\/div>\n
CREATE DATABASE db1 WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
CREATE DATABASE db2 WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
CREATE DATABASE mydb WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
CREATE DATABASE postgres_sample WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
[postgres@dbi-pg-essentials ~]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now let\u2019s dump all the user databases except db1 and db2.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials ~]$ <\/code>\/u01\/app\/postgres\/product\/12dev\/bin\/pg_dumpall<\/code>\u00a0 --exclude-database=db2 --exclude-database=db1 > without_db1_db2.sql<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We can effectively verify that the dump file contains instructions to create the databases mydb and postgres_sample. That\u2019s the expected result.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials ~]$ <\/code>grep<\/code> \"CREATE DATABASE\"<\/code> without_db1_db2.sql<\/code><\/div>\n
CREATE DATABASE mydb WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
CREATE DATABASE postgres_sample WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
[postgres@dbi-pg-essentials ~]$\u00a8<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

What is interesting is that we can use wildcard characters. The result above can obtained like following<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials ~]$\u00a0 <\/code>\/u01\/app\/postgres\/product\/12dev\/bin\/pg_dumpall<\/code>\u00a0 --exclude-database=db* > without_db_star.sql<\/code><\/div>\n
[postgres@dbi-pg-essentials ~]$ <\/code>grep<\/code> \"CREATE DATABASE\"<\/code> without_db_star.sql<\/code><\/div>\n
CREATE DATABASE mydb WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
CREATE DATABASE postgres_sample WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
[postgres@dbi-pg-essentials ~]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Let\u2019s say we want to dump all user databases except those whose names contain \u2018db\u2019<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials ~]$\u00a0 <\/code>\/u01\/app\/postgres\/product\/12dev\/bin\/pg_dumpall<\/code>\u00a0 --exclude-database=*db* > without_star_db_star.sql<\/code><\/div>\n
[postgres@dbi-pg-essentials ~]$ <\/code>grep<\/code> \"CREATE DATABASE\"<\/code> without_star_db_star.sql\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code><\/div>\n
\u00a0<\/code>CREATE DATABASE postgres_sample WITH TEMPLATE = template0 ENCODING = <\/code>'UTF8'<\/code> LC_COLLATE = <\/code>'en_US.UTF-8'<\/code> LC_CTYPE = <\/code>'en_US.UTF-8'<\/code>;<\/code><\/div>\n
[postgres@dbi-pg-essentials ~]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Conclusion:<\/h3>\n

In this blog we talked about the new option exclude-database for pg_dumpall in PostgreSQL 12.<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Up to PostgreSQL 11 pg_dump all was used to dump all PostgreSQL databases of a cluster into one script file. The script file then contains SQL commands that can be used as input to psql to restore the databases. It does this by calling pg_dump for each database in the cluster. PostgreSQL […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,83],"tags":[1580,1481,1581],"type_dbi":[],"class_list":["post-12286","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-postgresql","tag-pg_dumpall","tag-postgresql-12","tag-postgresql-dump"],"acf":[],"yoast_head":"\nPostgreSQL 12: New option -exclude-database for pg_dumpall - dbi Blog<\/title>\n<meta name=\"description\" content=\"Postgresql 12, pg_dumpall, PostgreSQL dump\" \/>\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-12-new-option-exclude-database-for-pg_dumpall\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 12: New option --exclude-database for pg_dumpall\" \/>\n<meta property=\"og:description\" content=\"Postgresql 12, pg_dumpall, PostgreSQL dump\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-03-02T21:12:41+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-15T14:32:39+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\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-12-new-option-exclude-database-for-pg_dumpall\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"PostgreSQL 12: New option –exclude-database for pg_dumpall\",\"datePublished\":\"2019-03-02T21:12:41+00:00\",\"dateModified\":\"2023-06-15T14:32:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/\"},\"wordCount\":258,\"commentCount\":0,\"keywords\":[\"pg_dumpall\",\"postgresql 12\",\"PostgreSQL dump\"],\"articleSection\":[\"Database Administration & Monitoring\",\"PostgreSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/\",\"name\":\"PostgreSQL 12: New option -exclude-database for pg_dumpall - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-03-02T21:12:41+00:00\",\"dateModified\":\"2023-06-15T14:32:39+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"Postgresql 12, pg_dumpall, PostgreSQL dump\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 12: New option –exclude-database for pg_dumpall\"}]},{\"@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\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL 12: New option -exclude-database for pg_dumpall - dbi Blog","description":"Postgresql 12, pg_dumpall, PostgreSQL dump","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-12-new-option-exclude-database-for-pg_dumpall\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 12: New option --exclude-database for pg_dumpall","og_description":"Postgresql 12, pg_dumpall, PostgreSQL dump","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/","og_site_name":"dbi Blog","article_published_time":"2019-03-02T21:12:41+00:00","article_modified_time":"2023-06-15T14:32:39+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"PostgreSQL 12: New option –exclude-database for pg_dumpall","datePublished":"2019-03-02T21:12:41+00:00","dateModified":"2023-06-15T14:32:39+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/"},"wordCount":258,"commentCount":0,"keywords":["pg_dumpall","postgresql 12","PostgreSQL dump"],"articleSection":["Database Administration & Monitoring","PostgreSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/","name":"PostgreSQL 12: New option -exclude-database for pg_dumpall - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-03-02T21:12:41+00:00","dateModified":"2023-06-15T14:32:39+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"Postgresql 12, pg_dumpall, PostgreSQL dump","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-new-option-exclude-database-for-pg_dumpall\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 12: New option –exclude-database for pg_dumpall"}]},{"@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\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12286","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\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=12286"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12286\/revisions"}],"predecessor-version":[{"id":25936,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12286\/revisions\/25936"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12286"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12286"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}