{"id":13421,"date":"2019-11-05T14:55:13","date_gmt":"2019-11-05T14:55:13","guid":{"rendered":"https:\/\/dbtut.com\/?p=13421"},"modified":"2021-09-19T11:08:39","modified_gmt":"2021-09-19T11:08:39","slug":"how-to-failover-and-failback-postgresql-replication","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/","title":{"rendered":"How To Failover and Failback PostgreSQL Replication"},"content":{"rendered":"

You may want to read the following articles about replication before reading this article.<\/p>\n

“How To Install PostgreSQL Replication By using archive_command On Centos<\/a>“,<\/p>\n

“How To Install PostgreSQL Replication With Replication Slots<\/a>”<\/p>\n

If you want to failover replication you should add trigger file to recovery.conf on secondary server. We have mentioned this in previous articles.<\/p>\n

To perform failover we will create a file on specified directory in trigger file.<\/p>\n

Failover PostgreSQL Replication<\/h1>\n

On Secondary Server(it will be new primary)<\/strong><\/p>\n

Connect to postgresql and execute the below command<\/p>\n

select pg_create_physical_replication_slot('old primary server name');<\/pre>\n
\"\"<\/p>\n
Then exit from postgresql and perform following steps:<\/p>\n
Stop Postgresql On Primary Server(it will be new secondary)<\/h3>\n
systemctl stop postgresql-11.service<\/pre>\n
Create trigger file on Secondary Server(it will be new primary) To perform Failover<\/strong><\/p>\n
With postgres user:<\/strong><\/p>\n
cd \/dbwhite\/dbtest\/11\/data\r\ntouch promotedbtest.data<\/pre>\n
After creating necessary file, failover process have performed. You can control recovery.conf file to understand the process completed succesfuly. If recovery.conf file changed to recovery.done, it means that failover process completed succesfully.<\/p>\n
\"\"<\/p>\n
Check replication status On New Primary Server<\/h3>\n
As you can see, the reverse replication did not occur automatically.<\/p>\n
\"\"<\/p>\n
Create Reverse Replication Again After Failover in PostgreSQL<\/h3>\n
Go to old master(new secondary) to install replication again between new master and new secondary server.<\/p>\n
On new Primary Server:<\/strong><\/p>\n
ALTER SYSTEM SET synchronous_commit TO 'remote_write';\r\nALTER SYSTEM SET synchronous_standby_names TO 'newsecondaryservername';\r\nselect pg_reload_conf();<\/pre>\n
\"\"<\/p>\n
On New Secondary<\/strong><\/p>\n
Create a recovery.conf file on data directory with below content<\/strong><\/p>\n
standby_mode = 'on'\r\nprimary_conninfo = 'user=replication passfile=''\/var\/lib\/pgsql\/.pgpass'' host=yournewprimaryserverip port=5432 sslmode=prefer sslcompression=0 krbsrvname=postgres target_session_attrs=any application_name='synchronous_standby_name_you_set_on_new_primary_server'\r\nprimary_slot_name = 'yournewsecondaryservername'\r\ntrigger_file='\/dbwhite\/dbats\/promotdbats.data'\r\nrecovery_target_timeline='latest'<\/pre>\n
It makes more sense to copy the recovery.done file in the new master from the new primary server to the new secondary with the following script. But when you copy, some of the above parameters will not be displayed. For example, recovery_target_timeline = ‘latest’<\/p>\n
Add these missing parameters to the new recovery.conf file.<\/p>\n
On new primary server with postgres<\/strong><\/p>\n
scp -p \/dbwhite\/dbyeni\/11\/data\/recovery.done newsecondaryip:\/dbwhite\/dbyeni\/11\/data\/recovery.conf<\/pre>\n
\"\"<\/p>\n
On New Secondary Server:<\/strong><\/p>\n
If you copy it instead of creating a new file, remember to change the application_name, host, and primary_slot_name in the recovery.conf file on the new secondary server.<\/p>\n
Edit postgresql.conf or postgresql.auto.conf (if you use auto conf) on data directory and remove below lines.<\/p>\n
vi postgresql.auto.conf<\/pre>\n
Delete below lines:<\/p>\n
synchronous_standby_names = 'yoursecondaryservername'\r\nsynchronous_commit TO 'remote_write';<\/pre>\n
On new Primary Server:<\/strong><\/p>\n
Then edit\u00a0 pg_hba.conf and check the below line. It should be as follows<\/p>\n
host\u00a0\u00a0\u00a0 replication\u00a0\u00a0\u00a0\u00a0 replication\u00a0\u00a0\u00a0\u00a0 newsecondaryserverip\/32\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 trust<\/pre>\n
On new secondary:<\/strong><\/p>\n
Finally start postgresql on new secondary<\/p>\n
systemctl start postgresql-11<\/pre>\n
Check PostgreSQL Replication Status on New Primary Server<\/h3>\n
Connect To PostgreSQL and run below statement.<\/p>\n
select * from pg_stat_replication;<\/pre>\n
If you have done everything in order, you will see a result like the following.<\/p>\n
\"\"<\/p>\n\n
\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"
You may want to read the following articles about replication before reading this article. “How To Install PostgreSQL Replication By using archive_command On Centos“, “How To Install PostgreSQL Replication With Replication Slots” If you want to failover replication you should add trigger file to recovery.conf on secondary server. We have mentioned this in previous articles. …<\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"author":1,"featured_media":13435,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[5],"tags":[5264,5265,5259,5263,5266,5262,5261,5269,5260,5268,5270,5271,5243,5251,5274,5275,5278,5267,230,5273,5272,5276],"class_list":["post-13421","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-postgres","tag-create-a-recovery-conf","tag-create-a-recovery-conf-file","tag-create-reverse-replication-again-after-failover-in-postgresql","tag-failback-postgresql-replication","tag-failback-replication","tag-failback-replication-in-postgresql","tag-failover-and-failback-postgresql-replication","tag-failover-postgresql","tag-failover-postgresql-replication","tag-failover-replication","tag-manual-failover","tag-manual-failover-postgresql","tag-pg_reload_conf","tag-pg_stat_replication","tag-postgresql-auto-conf","tag-primary_slot_name","tag-recovery_target_timeline","tag-reinstall-postgresql-replication-after-failover","tag-standby_mode","tag-synchronous_commit","tag-synchronous_standby_names","tag-trigger_file"],"aioseo_notices":[],"yoast_head":"\nHow To Failover and Failback PostgreSQL Replication - Database Tutorials<\/title>\n<meta name=\"description\" content=\"If you want to failover postgres replication you should add trigger file to recovery.conf on secondary server.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How To Failover and Failback PostgreSQL Replication - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"If you want to failover postgres replication you should add trigger file to recovery.conf on secondary server.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2019-11-05T14:55:13+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-09-19T11:08:39+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png\" \/>\n\t<meta property=\"og:image:width\" content=\"454\" \/>\n\t<meta property=\"og:image:height\" content=\"300\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"dbtut\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"dbtut\" \/>\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:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/\"},\"author\":{\"name\":\"dbtut\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/fc047c39e1e53dce28fc4253529ea408\"},\"headline\":\"How To Failover and Failback PostgreSQL Replication\",\"datePublished\":\"2019-11-05T14:55:13+00:00\",\"dateModified\":\"2021-09-19T11:08:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/\"},\"wordCount\":408,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png\",\"keywords\":[\"Create a recovery.conf\",\"Create a recovery.conf file\",\"Create Reverse Replication Again After Failover in PostgreSQL\",\"Failback PostgreSQL Replication\",\"Failback Replication\",\"Failback Replication in PostgreSQL\",\"Failover and Failback PostgreSQL Replication\",\"Failover PostgreSQL\",\"Failover PostgreSQL Replication\",\"Failover Replication\",\"manual failover\",\"manual failover postgresql\",\"pg_reload_conf()\",\"pg_stat_replication\",\"postgresql.auto.conf\",\"primary_slot_name\",\"recovery_target_timeline\",\"Reinstall PostgreSQL Replication After Failover\",\"standby_mode\",\"synchronous_commit\",\"synchronous_standby_names\",\"trigger_file\"],\"articleSection\":[\"PostgreSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/\",\"name\":\"How To Failover and Failback PostgreSQL Replication - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png\",\"datePublished\":\"2019-11-05T14:55:13+00:00\",\"dateModified\":\"2021-09-19T11:08:39+00:00\",\"description\":\"If you want to failover postgres replication you should add trigger file to recovery.conf on secondary server.\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png\",\"width\":454,\"height\":300},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How To Failover and Failback PostgreSQL Replication\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/fc047c39e1e53dce28fc4253529ea408\",\"name\":\"dbtut\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c322c32021bf651d9e103b183963c479a9c9791ead0715f4348203496c39aa54?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c322c32021bf651d9e103b183963c479a9c9791ead0715f4348203496c39aa54?s=96&d=mm&r=g\",\"caption\":\"dbtut\"},\"description\":\"We are a team with over 10 years of database management and BI experience. Our Expertises: Oracle, SQL Server, PostgreSQL, MySQL, MongoDB, Elasticsearch, Kibana, Grafana.\",\"sameAs\":[\"http:\/\/NurullahCAKIR\"],\"url\":\"https:\/\/dbtut.com\/index.php\/author\/dbtut\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How To Failover and Failback PostgreSQL Replication - Database Tutorials","description":"If you want to failover postgres replication you should add trigger file to recovery.conf on secondary server.","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:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/","og_locale":"en_US","og_type":"article","og_title":"How To Failover and Failback PostgreSQL Replication - Database Tutorials","og_description":"If you want to failover postgres replication you should add trigger file to recovery.conf on secondary server.","og_url":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/","og_site_name":"Database Tutorials","article_published_time":"2019-11-05T14:55:13+00:00","article_modified_time":"2021-09-19T11:08:39+00:00","og_image":[{"width":454,"height":300,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png","type":"image\/png"}],"author":"dbtut","twitter_card":"summary_large_image","twitter_misc":{"Written by":"dbtut","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/"},"author":{"name":"dbtut","@id":"https:\/\/dbtut.com\/#\/schema\/person\/fc047c39e1e53dce28fc4253529ea408"},"headline":"How To Failover and Failback PostgreSQL Replication","datePublished":"2019-11-05T14:55:13+00:00","dateModified":"2021-09-19T11:08:39+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/"},"wordCount":408,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png","keywords":["Create a recovery.conf","Create a recovery.conf file","Create Reverse Replication Again After Failover in PostgreSQL","Failback PostgreSQL Replication","Failback Replication","Failback Replication in PostgreSQL","Failover and Failback PostgreSQL Replication","Failover PostgreSQL","Failover PostgreSQL Replication","Failover Replication","manual failover","manual failover postgresql","pg_reload_conf()","pg_stat_replication","postgresql.auto.conf","primary_slot_name","recovery_target_timeline","Reinstall PostgreSQL Replication After Failover","standby_mode","synchronous_commit","synchronous_standby_names","trigger_file"],"articleSection":["PostgreSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/","url":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/","name":"How To Failover and Failback PostgreSQL Replication - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png","datePublished":"2019-11-05T14:55:13+00:00","dateModified":"2021-09-19T11:08:39+00:00","description":"If you want to failover postgres replication you should add trigger file to recovery.conf on secondary server.","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/11\/Ads\u0131z-4.png","width":454,"height":300},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2019\/11\/05\/how-to-failover-and-failback-postgresql-replication\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"How To Failover and Failback PostgreSQL Replication"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/fc047c39e1e53dce28fc4253529ea408","name":"dbtut","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/c322c32021bf651d9e103b183963c479a9c9791ead0715f4348203496c39aa54?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c322c32021bf651d9e103b183963c479a9c9791ead0715f4348203496c39aa54?s=96&d=mm&r=g","caption":"dbtut"},"description":"We are a team with over 10 years of database management and BI experience. Our Expertises: Oracle, SQL Server, PostgreSQL, MySQL, MongoDB, Elasticsearch, Kibana, Grafana.","sameAs":["http:\/\/NurullahCAKIR"],"url":"https:\/\/dbtut.com\/index.php\/author\/dbtut\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/13421","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=13421"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/13421\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/13435"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=13421"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=13421"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=13421"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}