{"id":30204,"date":"2024-01-18T11:41:11","date_gmt":"2024-01-18T10:41:11","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=30204"},"modified":"2024-01-18T11:41:11","modified_gmt":"2024-01-18T10:41:11","slug":"postgresql-17-incremental-backups-system-information-functions","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/","title":{"rendered":"PostgreSQL 17: Incremental backups, system information functions"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In the <a href=\"https:\/\/www.dbi-services.com\/blog\/postgresql-17-support-for-incremental-backups\/\" target=\"_blank\" rel=\"noreferrer noopener\">first post about incremental backups<\/a> we&#8217;ve looked at how you can do incremental backups in general starting with PostgreSQL 17, probably, if it does not get reverted for some reason until PostgreSQL 17 is released. In the <a href=\"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-and-backup-chains\/\" target=\"_blank\" rel=\"noreferrer noopener\">second post about incremental backups<\/a> we&#8217;ve looked at backup chains and the choices you have for combining backups to create a starting point for new incremental backups. In this post we&#8217;ll look at the <a href=\"https:\/\/www.postgresql.org\/docs\/devel\/functions-info.html\" target=\"_blank\" rel=\"noreferrer noopener\">new system information functions<\/a> which have been added with this feature.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We&#8217;ll start with a complete new cluster having &#8220;<a href=\"https:\/\/www.postgresql.org\/docs\/devel\/runtime-config-wal.html#GUC-SUMMARIZE-WAL\" target=\"_blank\" rel=\"noreferrer noopener\">summarize_wal<\/a>&#8221; enabled:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# \\dconfig *summa*\nList of configuration parameters\n       Parameter       | Value \n-----------------------+-------\n summarize_wal         | on\n wal_summary_keep_time | 10d\n(2 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">WAL summaries are written to pg_wal\/summaries and of course we do not see anything there right now as we did not do anything with this cluster:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,8]; title: ; notranslate\" title=\"\">\npostgres=# \\! ls -la $PGDATA\/pg_wal\/\ntotal 16400\ndrwx------  4 postgres postgres     4096 Jan 18 10:51 .\ndrwx------ 20 postgres postgres     4096 Jan 18 10:51 ..\n-rw-------  1 postgres postgres 16777216 Jan 18 10:53 000000010000000000000001\ndrwx------  2 postgres postgres     4096 Jan 18 10:51 archive_status\ndrwx------  2 postgres postgres     4096 Jan 18 10:51 summaries\npostgres=# \\! ls -la $PGDATA\/pg_wal\/summaries\ntotal 44\ndrwx------ 2 postgres postgres 4096 Jan 18 10:51 .\ndrwx------ 4 postgres postgres 4096 Jan 18 10:51 ..\n-rw------- 1 postgres postgres 4808 Jan 18 10:51 00000001000000000100002800000000010B3098.summary\n-rw------- 1 postgres postgres 4944 Jan 18 10:51 0000000100000000010B309800000000014E8838.summary\n-rw------- 1 postgres postgres   32 Jan 18 10:51 0000000100000000014E883800000000014E8938.summary\n-rw------- 1 postgres postgres  230 Jan 18 10:51 0000000100000000014E893800000000014EF360.summary\n-rw------- 1 postgres postgres   32 Jan 18 10:51 0000000100000000014EF36000000000014EF460.summary\n-rw------- 1 postgres postgres   88 Jan 18 10:51 0000000100000000014EF46000000000014EF798.summary\n-rw------- 1 postgres postgres   32 Jan 18 10:51 0000000100000000014EF79800000000014EF810.summary\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Oh, this is not true at all. We do see quite some files there even though nothing happened from the user perspective. Well, this is the perfect use case to start with the three system information functions which have been added with this feature. Let&#8217;s start with &#8220;<code>pg_available_wal_summaries<\/code> ()&#8221;, which gives us the same picture than the file system but comes with additional information:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; title: ; notranslate\" title=\"\">\npostgres=# select * from pg_available_wal_summaries ();\n tli | start_lsn |  end_lsn  \n-----+-----------+-----------\n   1 | 0\/14EF360 | 0\/14EF460\n   1 | 0\/14E8938 | 0\/14EF360\n   1 | 0\/1000028 | 0\/10B3098\n   1 | 0\/14EF460 | 0\/14EF798\n   1 | 0\/14E8838 | 0\/14E8938\n   1 | 0\/10B3098 | 0\/14E8838\n   1 | 0\/14EF798 | 0\/14EF810\n(7 rows)\n\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">This looks a bit strange as we do not see any connection from one row to the next row. In other words: Isn&#8217;t it expected that this describes a chain? The &#8220;end_lsn&#8221; of one row should be the &#8220;start_lsn&#8221; of the next row? Let&#8217;s sort by &#8220;start_lsn&#8221;, as we are on the same timeline (tli) this gives us the result which is expected:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# select * from pg_available_wal_summaries () order by start_lsn;\n tli | start_lsn |  end_lsn  \n-----+-----------+-----------\n   1 | 0\/1000028 | 0\/10B3098\n   1 | 0\/10B3098 | 0\/14E8838\n   1 | 0\/14E8838 | 0\/14E8938\n   1 | 0\/14E8938 | 0\/14EF360\n   1 | 0\/14EF360 | 0\/14EF460\n   1 | 0\/14EF460 | 0\/14EF798\n   1 | 0\/14EF798 | 0\/14EF810\n(7 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Now we have the same picture as on the file system, e.g. the &#8220;end_lsn&#8221; of the first row is the &#8220;start_lsn&#8221; of the next row and this continues to the end of the summaries:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# \\! ls -la $PGDATA\/pg_wal\/summaries\ntotal 44\ndrwx------ 2 postgres postgres 4096 Jan 18 10:51 .\ndrwx------ 4 postgres postgres 4096 Jan 18 10:51 ..\n-rw------- 1 postgres postgres 4808 Jan 18 10:51 00000001000000000100002800000000010B3098.summary\n-rw------- 1 postgres postgres 4944 Jan 18 10:51 0000000100000000010B309800000000014E8838.summary\n-rw------- 1 postgres postgres   32 Jan 18 10:51 0000000100000000014E883800000000014E8938.summary\n-rw------- 1 postgres postgres  230 Jan 18 10:51 0000000100000000014E893800000000014EF360.summary\n-rw------- 1 postgres postgres   32 Jan 18 10:51 0000000100000000014EF36000000000014EF460.summary\n-rw------- 1 postgres postgres   88 Jan 18 10:51 0000000100000000014EF46000000000014EF798.summary\n-rw------- 1 postgres postgres   32 Jan 18 10:51 0000000100000000014EF79800000000014EF810.summary\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">This is also how the file names on disk are made up: First you have the beginning and ending timelime, after the beginning and ending lsn (<a href=\"https:\/\/www.postgresql.org\/docs\/devel\/datatype-pg-lsn.html\">Log Sequence Number<\/a>).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The next function we can have a look at it <code>pg_wal_summary_contents<\/code> ( <em><code>tli<\/code><\/em> <code>bigint<\/code>, <em><code>start_lsn<\/code><\/em> <code>pg_lsn<\/code>, <em><code>end_lsn<\/code><\/em> <code>pg_lsn<\/code> ). This function will give us some insights into what is in a summary, e.g. using the first entry from above:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; title: ; notranslate\" title=\"\">\npostgres=# select * from pg_wal_summary_contents ( 1, &#039;0\/1000028&#039;, &#039;0\/10B3098&#039; ) ;\n relfilenode | reltablespace | reldatabase | relforknumber | relblocknumber | is_limit_block \n-------------+---------------+-------------+---------------+----------------+----------------\n         112 |          1663 |           1 |             0 |              0 | f\n         113 |          1663 |           1 |             0 |              0 | f\n         174 |          1663 |           1 |             0 |              0 | f\n         175 |          1663 |           1 |             0 |              0 | f\n         548 |          1663 |           1 |             0 |              0 | f\n         549 |          1663 |           1 |             0 |              0 | f\n...\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">What does this mean? First of all this is about the template1 database:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; title: ; notranslate\" title=\"\">\npostgres=# select oid,datname from pg_database;\n oid |  datname  \n-----+-----------\n   5 | postgres\n   1 | template1\n   4 | template0\n(3 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">The tablespace is pg_default:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# select oid,spcname from pg_tablespace ;\n oid  |  spcname   \n------+------------\n 1663 | pg_default\n 1664 | pg_global\n(2 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">The &#8220;relfinode&#8221; column describes the file on disk, e.g.:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# \\! ls -la $PGDATA\/base\/1\/112*\n-rw------- 1 postgres postgres 8192 Jan 18 10:51 \/u02\/pgdata\/PGDEV\/base\/1\/112\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">&#8220;relblocknumber&#8221; mentions the block which has changed. &#8220;is_limit_block&#8221; <a href=\"https:\/\/www.postgresql.org\/docs\/devel\/functions-info.html#FUNCTIONS-INFO-WAL-SUMMARY\" target=\"_blank\" rel=\"noreferrer noopener\">means<\/a> &#8220;Each row with <code>is_limit_block<\/code> false indicates that the block identified by the remaining output columns was modified by at least one WAL record within the range of records summarized by this file. Each row with <code>is_limit_block<\/code> true indicates either that (a) the relation fork was truncated to the length given by <code>relblocknumber<\/code> within the relevant range of WAL records or (b) that the relation fork was created or dropped within the relevant range of WAL records; in such cases, <code>relblocknumber<\/code> will be zero.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Lets do a simple test to see what this really means. We create a simple table with one row:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,3,5]; title: ; notranslate\" title=\"\">\npostgres=# create table t ( a int );\nCREATE TABLE\npostgres=# insert into t values (1);\nINSERT 0 1\npostgres=# select pg_relation_filepath(&#039;t&#039;);\n pg_relation_filepath \n----------------------\n base\/5\/16388\n(1 row)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">For this we should see a new entry in the output of pg_wal_summary_contents if we ask for the last summary file:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# select * from pg_wal_summary_contents ( 1, &#039;0\/14EF810&#039;, &#039;0\/1557C00&#039; ) where relfilenode = 16388;\n relfilenode | reltablespace | reldatabase | relforknumber | relblocknumber | is_limit_block \n-------------+---------------+-------------+---------------+----------------+----------------\n(0 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">We don&#8217;t see anything and the reason is that a new summary file has not yet been written, lets force this and check again:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,3,17]; title: ; notranslate\" title=\"\">\npostgres=# checkpoint;\nCHECKPOINT\npostgres=# select * from pg_available_wal_summaries () order by start_lsn;\n tli | start_lsn |  end_lsn  \n-----+-----------+-----------\n   1 | 0\/1000028 | 0\/10B3098\n   1 | 0\/10B3098 | 0\/14E8838\n   1 | 0\/14E8838 | 0\/14E8938\n   1 | 0\/14E8938 | 0\/14EF360\n   1 | 0\/14EF360 | 0\/14EF460\n   1 | 0\/14EF460 | 0\/14EF798\n   1 | 0\/14EF798 | 0\/14EF810\n   1 | 0\/14EF810 | 0\/1557C00\n   1 | 0\/1557C00 | 0\/15598C8\n(9 rows)\n\npostgres=# select * from pg_wal_summary_contents ( 1, &#039;0\/1557C00&#039;, &#039;0\/15598C8&#039; ) where relfilenode = 16388;\n relfilenode | reltablespace | reldatabase | relforknumber | relblocknumber | is_limit_block \n-------------+---------------+-------------+---------------+----------------+----------------\n       16388 |          1663 |           5 |             0 |              0 | f\n(1 row)\n\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Lets add some more data and see how this is recorded in the wal summaries:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; title: ; notranslate\" title=\"\">\npostgres=# insert into t select * from generate_series(1,1000000);\nINSERT 0 1000000\npostgres=# checkpoint;\nCHECKPOINT\npostgres=# select * from pg_available_wal_summaries () order by start_lsn;\n tli | start_lsn |  end_lsn  \n-----+-----------+-----------\n   1 | 0\/1000028 | 0\/10B3098\n   1 | 0\/10B3098 | 0\/14E8838\n   1 | 0\/14E8838 | 0\/14E8938\n   1 | 0\/14E8938 | 0\/14EF360\n   1 | 0\/14EF360 | 0\/14EF460\n   1 | 0\/14EF460 | 0\/14EF798\n   1 | 0\/14EF798 | 0\/14EF810\n   1 | 0\/14EF810 | 0\/1557C00\n   1 | 0\/1557C00 | 0\/15598C8\n   1 | 0\/15598C8 | 0\/5290968\n(10 rows)\n\npostgres=# select * from pg_wal_summary_contents ( 1, &#039;0\/15598C8&#039;, &#039;0\/5290968&#039; ) where relfilenode = 16388;\n relfilenode | reltablespace | reldatabase | relforknumber | relblocknumber | is_limit_block \n-------------+---------------+-------------+---------------+----------------+----------------\n       16388 |          1663 |           5 |             0 |              0 | f\n       16388 |          1663 |           5 |             0 |              1 | f\n       16388 |          1663 |           5 |             0 |              2 | f\n       16388 |          1663 |           5 |             0 |              3 | f\n       16388 |          1663 |           5 |             0 |              4 | f\n       16388 |          1663 |           5 |             0 |              5 | f\n       16388 |          1663 |           5 |             0 |              6 | f\n...\n       16388 |          1663 |           5 |             0 |           4420 | f\n       16388 |          1663 |           5 |             0 |           4421 | f\n       16388 |          1663 |           5 |             0 |           4422 | f\n       16388 |          1663 |           5 |             0 |           4423 | f\n       16388 |          1663 |           5 |             0 |           4424 | f\n(4425 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Does this mean we&#8217;ve modified 4424 blocks in that table? Yes, it does:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,6,10]; title: ; notranslate\" title=\"\">\npostgres=# select pg_relation_filepath(&#039;t&#039;);\n pg_relation_filepath \n----------------------\n base\/5\/16388\n(1 row)\npostgres=# \\! ls -la $PGDATA\/base\/5\/16388*\n-rw------- 1 postgres postgres 36249600 Jan 18 11:23 \/u02\/pgdata\/PGDEV\/base\/5\/16388\n-rw------- 1 postgres postgres    32768 Jan 18 11:23 \/u02\/pgdata\/PGDEV\/base\/5\/16388_fsm\n-rw------- 1 postgres postgres     8192 Jan 18 11:23 \/u02\/pgdata\/PGDEV\/base\/5\/16388_vm\npostgres=# select 36249600\/8192;\n ?column? \n----------\n     4425\n(1 row)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">An incremental backup would need to contain all those blocks as they&#8217;ve changed since the last full backup.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The last function gives the state of the summarizer process:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# select * from pg_get_wal_summarizer_state () ;\n summarized_tli | summarized_lsn | pending_lsn | summarizer_pid \n----------------+----------------+-------------+----------------\n              1 | 0\/77DC3C0      | 0\/77DE570   |           1638\n(1 row)\n\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Pretty straight forward: The timeline, the last LSN up to which summaries have been written and pending_lsn means the last lsn the summarizer has consumed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the first post about incremental backups we&#8217;ve looked at how you can do incremental backups in general starting with PostgreSQL 17, probably, if it does not get reverted for some reason until PostgreSQL 17 is released. In the second post about incremental backups we&#8217;ve looked at backup chains and the choices you have for&hellip;&nbsp;<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[4133],"tags":[],"class_list":["post-30204","post","type-post","status-publish","format-standard","category-database"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.9) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>PostgreSQL 17: Incremental backups, system information functions - dbi services 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-17-incremental-backups-system-information-functions\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 17: Incremental backups, system information functions\" \/>\n<meta property=\"og:description\" content=\"In the first post about incremental backups we&#8217;ve looked at how you can do incremental backups in general starting with PostgreSQL 17, probably, if it does not get reverted for some reason until PostgreSQL 17 is released. In the second post about incremental backups we&#8217;ve looked at backup chains and the choices you have for&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2024-01-18T10:41:11+00:00\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Open source 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-17-incremental-backups-system-information-functions\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\"},\"headline\":\"PostgreSQL 17: Incremental backups, system information functions\",\"datePublished\":\"2024-01-18T10:41:11+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/\"},\"wordCount\":628,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"articleSection\":[\"Database\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/\",\"name\":\"PostgreSQL 17: Incremental backups, system information functions - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2024-01-18T10:41:11+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-incremental-backups-system-information-functions\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 17: Incremental backups, system information functions\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"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\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"caption\":\"Open source Team\"},\"description\":\"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/open-source-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL 17: Incremental backups, system information functions - dbi services 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-17-incremental-backups-system-information-functions\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 17: Incremental backups, system information functions","og_description":"In the first post about incremental backups we&#8217;ve looked at how you can do incremental backups in general starting with PostgreSQL 17, probably, if it does not get reverted for some reason until PostgreSQL 17 is released. In the second post about incremental backups we&#8217;ve looked at backup chains and the choices you have for&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2024-01-18T10:41:11+00:00","author":"Open source Team","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Open source Team","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a"},"headline":"PostgreSQL 17: Incremental backups, system information functions","datePublished":"2024-01-18T10:41:11+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/"},"wordCount":628,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"articleSection":["Database"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/","name":"PostgreSQL 17: Incremental backups, system information functions - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2024-01-18T10:41:11+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-incremental-backups-system-information-functions\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 17: Incremental backups, system information functions"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"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":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","caption":"Open source Team"},"description":"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.","url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30204","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\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=30204"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30204\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=30204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=30204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=30204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}