{"id":9950,"date":"2017-04-13T14:03:33","date_gmt":"2017-04-13T12:03:33","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/"},"modified":"2017-04-13T14:03:33","modified_gmt":"2017-04-13T12:03:33","slug":"in-core-logical-replication-will-hit-postgresql-10","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/","title":{"rendered":"In-core logical replication will hit PostgreSQL 10"},"content":{"rendered":"<p>Finally in PostgreSQL 10 (expected to be released this September) a long awaited feature will probably appear: In-core logical replication. PostgreSQL supports physical replication since version 9.0 and now the next step happened with the implementation of logical replication. This will be a major help in upgrading PostgreSQL instances from one version to another with no (or almost no) downtime. In addition this can be used to consolidate data from various instances into one instance for reporting purposes or you can use it to distribute only a subset of your data to selected users on other instances. In contrast to physical replication logical replication works on the table level so you can replicate changes in one or more tables, one database are all databases in a PostgreSQL instance which is quite flexible.<\/p>\n<p>In PostgreSQL logical replication is implemented using a publisher and subscriber model. This mean the publisher is the one who will send the data and the subscriber is the one who will receive and apply the changes. A subscriber can be a publisher as well so you can build cascading logical replication. Here is an overview of a possible setup:<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg-logocal-replication-overview.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg-logocal-replication-overview.png\" alt=\"pg-logocal-replication-overview\" width=\"838\" height=\"529\" class=\"aligncenter size-full wp-image-15873\" \/><\/a><\/p>\n<p>For setting up logical replication when you do not start with an empty database you&#8217;ll need to initially load the database where you want to replicate to. How can you do that? I have two PostgreSQL 10 instances (build from the git sources) running on the same host:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Role<\/th>\n<th>Port<\/th>\n<\/tr>\n<tr>\n<td>Publisher<\/td>\n<td>6666<\/td>\n<\/tr>\n<tr>\n<td>Subsriber<\/td>\n<td>6667<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Lets assume we have this sample setup on the publisher instance:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">drop table if exists t1;\ncreate table t1 ( a int primary key\n                , b varchar(100)\n                );\nwith generator as \n ( select a.*\n     from generate_series ( 1, 5000000 ) a\n    order by random()\n )\ninsert into t1 ( a,b ) \n     select a\n          , md5(a::varchar)\n       from generator;\nselect * from pg_size_pretty ( pg_relation_size ('t1' ));\n<\/pre>\n<p>On the subscriber instance there is the same table, but empty:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">create table t1 ( a int primary key\n                , b varchar(100)\n                );\n<\/pre>\n<p>Before we start with the initial load lets take a look at the process list:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [8,15]\">\npostgres@pgbox:\/home\/postgres\/ [PUBLISHER] ps -ef | egrep \"PUBLISHER|SUBSCRIBER\"\npostgres 17311     1  0 11:33 pts\/0    00:00:00 \/u01\/app\/postgres\/product\/dev\/db_01\/bin\/postgres -D \/u02\/pgdata\/PUBLISHER\npostgres 17313 17311  0 11:33 ?        00:00:00 postgres: PUBLISHER: checkpointer process   \npostgres 17314 17311  0 11:33 ?        00:00:00 postgres: PUBLISHER: writer process   \npostgres 17315 17311  0 11:33 ?        00:00:00 postgres: PUBLISHER: wal writer process   \npostgres 17316 17311  0 11:33 ?        00:00:00 postgres: PUBLISHER: autovacuum launcher process   \npostgres 17317 17311  0 11:33 ?        00:00:00 postgres: PUBLISHER: stats collector process   \npostgres 17318 17311  0 11:33 ?        00:00:00 postgres: PUBLISHER: bgworker: logical replication launcher   \npostgres 17321     1  0 11:33 pts\/1    00:00:00 \/u01\/app\/postgres\/product\/dev\/db_01\/bin\/postgres -D \/u02\/pgdata\/SUBSCRIBER\npostgres 17323 17321  0 11:33 ?        00:00:00 postgres: SUBSCRIBER: checkpointer process   \npostgres 17324 17321  0 11:33 ?        00:00:00 postgres: SUBSCRIBER: writer process   \npostgres 17325 17321  0 11:33 ?        00:00:00 postgres: SUBSCRIBER: wal writer process   \npostgres 17326 17321  0 11:33 ?        00:00:00 postgres: SUBSCRIBER: autovacuum launcher process   \npostgres 17327 17321  0 11:33 ?        00:00:00 postgres: SUBSCRIBER: stats collector process   \npostgres 17328 17321  0 11:33 ?        00:00:00 postgres: SUBSCRIBER: bgworker: logical replication launcher   \n<\/pre>\n<p>You&#8217;ll notice that there is a new background process called &#8220;bgworker: logical replication launcher&#8221;. We&#8217;ll come back to that later.<\/p>\n<p>Time to create our first publication on the publisher with the <a href=\"https:\/\/www.postgresql.org\/docs\/devel\/static\/sql-createpublication.html\" target=\"_blank\">create publication<\/a> command:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres@pgbox:\/u02\/pgdata\/PUBLISHER\/ [PUBLISHER] psql -X postgres\npsql (10devel)\nType \"help\" for help.\n\npostgres=# create publication my_first_publication for table t1;\nCREATE PUBLICATION\n<\/pre>\n<p>On the subscriber we need to create a subscription by using the <a href=\"https:\/\/www.postgresql.org\/docs\/devel\/static\/sql-createsubscription.html\" target=\"_blank\">create subscription<\/a> command:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres@pgbox:\/u02\/pgdata\/SUBSCRIBER\/ [SUBSCRIBER] psql -X postgres\npsql (10devel)\nType \"help\" for help.\n\npostgres=# create subscription my_first_subscription connection 'host=localhost port=6666 dbname=postgres user=postgres' publication my_first_publication;\nERROR:  could not create replication slot \"my_first_subscription\": ERROR:  logical decoding requires wal_level &gt;= logical\n<\/pre>\n<p>Ok, good hint. After changing that on both instances:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres@pgbox:\/home\/postgres\/ [SUBSCRIBER] psql -X postgres\npsql (10devel)\nType \"help\" for help.\n\npostgres=# create subscription my_first_subscription connection 'host=localhost port=6666 dbname=postgres user=postgres' publication my_first_publication;\nCREATE SUBSCRIPTION\n<\/pre>\n<p>If you are not on super fast hardware and check the process list again you&#8217;ll see something like this:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres 19465 19079 19 11:58 ?        00:00:04 postgres: SUBSCRIBER: bgworker: logical replication worker for subscription 16390 sync 16384  \n<\/pre>\n<p>On the subscriber the &#8220;logical replication launcher&#8221; background process launched a worker process and syncs the table automatically (this can be avoided by using the &#8220;NOCOPY DATA&#8221;):<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# show port;\n port \n------\n 6667\n(1 row)\n\npostgres=# select count(*) from t1;\n  count  \n---------\n 5000000\n(1 row)\n<\/pre>\n<p>Wow, that was really easy. You can find more details in the logfile of the subscriber instance:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n2017-04-13 11:58:15.099 CEST - 1 - 19087 -  - @ LOG:  starting logical replication worker for subscription \"my_first_subscription\"\n2017-04-13 11:58:15.101 CEST - 1 - 19463 -  - @ LOG:  logical replication apply for subscription my_first_subscription started\n2017-04-13 11:58:15.104 CEST - 2 - 19463 -  - @ LOG:  starting logical replication worker for subscription \"my_first_subscription\"\n2017-04-13 11:58:15.105 CEST - 1 - 19465 -  - @ LOG:  logical replication sync for subscription my_first_subscription, table t1 started\n2017-04-13 11:59:03.373 CEST - 1 - 19082 -  - @ LOG:  checkpoint starting: xlog\n2017-04-13 11:59:37.985 CEST - 2 - 19082 -  - @ LOG:  checkpoint complete: wrote 14062 buffers (85.8%); 1 transaction log file(s) added, 0 removed, 0 recycled; write=26.959 s, sync=2.291 s, total=34.740 s; sync files=13, longest=1.437 s, average=0.171 s; distance=405829 kB, estimate=405829 kB\n2017-04-13 12:02:23.728 CEST - 2 - 19465 -  - @ LOG:  logical replication synchronization worker finished processing\n<\/pre>\n<p>On the publisher instance you get another process for sending the changes to the subscriber:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres 19464 18318  0 11:58 ?        00:00:00 postgres: PUBLISHER: wal sender process postgres ::1(41768) idle\n<\/pre>\n<p>Changes to the table on the publisher should now get replicated to the subscriber node:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# show port;\n port \n------\n 6666\n(1 row)\npostgres=# insert into t1 (a,b) values (-1,'aaaaa');\nINSERT 0 1\npostgres=# update t1 set b='bbbbb' where a=-1;\nUPDATE 1\n<\/pre>\n<p>On the subscriber node:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# show port;\n port \n------\n 6667\n(1 row)\n\npostgres=# select * from t1 where a = -1;\n a  |   b   \n----+-------\n -1 | aaaaa\n(1 row)\n\npostgres=# select * from t1 where a = -1;\n a  |   b   \n----+-------\n -1 | bbbbb\n(1 row)\n<\/pre>\n<p>As mentioned initially you can make the subscriber a publisher and the publisher a subscriber at the same time. So when we create this table on both instances:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\ncreate table t2 ( a int primary key );\n<\/pre>\n<p>Then create a publication on the subscriber node: <\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# create table t2 ( a int primary key );\nCREATE TABLE\npostgres=# show port;\n port \n------\n 6667\n(1 row)\n\npostgres=# create publication my_second_publication for table t2;\nCREATE PUBLICATION\npostgres=# \n<\/pre>\n<p>Then create the subscription to that on the publisher node:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# show port;\n port \n------\n 6666\n(1 row)\n\npostgres=# create subscription my_second_subscription connection 'host=localhost port=6667 dbname=postgres user=postgres' publication my_second_publication;\nCREATE SUBSCRIPTION\n<\/pre>\n<p>&#8230; we have a second logical replication the other way around:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# show port;\n port \n------\n 6667\n(1 row)\npostgres=# insert into t2 values ( 1 );\nINSERT 0 1\npostgres=# insert into t2 values ( 2 );\nINSERT 0 1\npostgres=# \n<\/pre>\n<p>On the other instance:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# show port;\n port \n------\n 6666\n(1 row)\n\npostgres=# select * from t2;\n a \n---\n 1\n 2\n(2 rows)\n<\/pre>\n<p>There are two new catalog views which give you information about subscriptions and publications:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select * from pg_subscription;\n subdbid |        subname         | subowner | subenabled |                      subconninfo                       |      subslotname       |     subpublications     \n---------+------------------------+----------+------------+--------------------------------------------------------+------------------------+-------------------------\n   13216 | my_second_subscription |       10 | t          | host=localhost port=6667 dbname=postgres user=postgres | my_second_subscription | {my_second_publication}\n(1 row)\n\npostgres=# select * from pg_publication;\n       pubname        | pubowner | puballtables | pubinsert | pubupdate | pubdelete \n----------------------+----------+--------------+-----------+-----------+-----------\n my_first_publication |       10 | f            | t         | t         | t\n(1 row)\n<\/pre>\n<p>What a cool feature and so easy to use. Thanks to all who brought that into PostgreSQL 10, great work.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Finally in PostgreSQL 10 (expected to be released this September) a long awaited feature will probably appear: In-core logical replication. PostgreSQL supports physical replication since version 9.0 and now the next step happened with the implementation of logical replication. This will be a major help in upgrading PostgreSQL instances from one version to another with&hellip;&nbsp;<\/p>\n","protected":false},"author":28,"featured_media":9952,"comment_status":"open","ping_status":"open","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":[1074],"class_list":["post-9950","post","type-post","status-publish","format-standard","has-post-thumbnail","category-database","tag-logical-replication"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>In-core logical replication will hit PostgreSQL 10 - 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\/in-core-logical-replication-will-hit-postgresql-10\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"In-core logical replication will hit PostgreSQL 10\" \/>\n<meta property=\"og:description\" content=\"Finally in PostgreSQL 10 (expected to be released this September) a long awaited feature will probably appear: In-core logical replication. PostgreSQL supports physical replication since version 9.0 and now the next step happened with the implementation of logical replication. This will be a major help in upgrading PostgreSQL instances from one version to another with&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/\" \/>\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=\"2017-04-13T12:03:33+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg_logical_replication_overview.png\" \/>\n\t<meta property=\"og:image:width\" content=\"900\" \/>\n\t<meta property=\"og:image:height\" content=\"519\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\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=\"6 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\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\"},\"headline\":\"In-core logical replication will hit PostgreSQL 10\",\"datePublished\":\"2017-04-13T12:03:33+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/\"},\"wordCount\":536,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/04\\\/pg_logical_replication_overview.png\",\"keywords\":[\"Logical Replication\"],\"articleSection\":[\"Database\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/\",\"name\":\"In-core logical replication will hit PostgreSQL 10 - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/04\\\/pg_logical_replication_overview.png\",\"datePublished\":\"2017-04-13T12:03:33+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/04\\\/pg_logical_replication_overview.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/04\\\/pg_logical_replication_overview.png\",\"width\":900,\"height\":519},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/in-core-logical-replication-will-hit-postgresql-10\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"In-core logical replication will hit PostgreSQL 10\"}]},{\"@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":"In-core logical replication will hit PostgreSQL 10 - 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\/in-core-logical-replication-will-hit-postgresql-10\/","og_locale":"en_US","og_type":"article","og_title":"In-core logical replication will hit PostgreSQL 10","og_description":"Finally in PostgreSQL 10 (expected to be released this September) a long awaited feature will probably appear: In-core logical replication. PostgreSQL supports physical replication since version 9.0 and now the next step happened with the implementation of logical replication. This will be a major help in upgrading PostgreSQL instances from one version to another with&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2017-04-13T12:03:33+00:00","og_image":[{"width":900,"height":519,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg_logical_replication_overview.png","type":"image\/png"}],"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":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a"},"headline":"In-core logical replication will hit PostgreSQL 10","datePublished":"2017-04-13T12:03:33+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/"},"wordCount":536,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg_logical_replication_overview.png","keywords":["Logical Replication"],"articleSection":["Database"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/","url":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/","name":"In-core logical replication will hit PostgreSQL 10 - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg_logical_replication_overview.png","datePublished":"2017-04-13T12:03:33+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg_logical_replication_overview.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/04\/pg_logical_replication_overview.png","width":900,"height":519},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/in-core-logical-replication-will-hit-postgresql-10\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"In-core logical replication will hit PostgreSQL 10"}]},{"@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\/9950","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=9950"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9950\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/9952"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=9950"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=9950"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=9950"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}