{"id":8224,"date":"2020-01-21T10:49:11","date_gmt":"2020-01-21T09:49:11","guid":{"rendered":"https:\/\/blog.capdata.fr\/?p=8224"},"modified":"2021-02-26T14:45:48","modified_gmt":"2021-02-26T13:45:48","slug":"aws-rds-les-extensions-postgresql","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/","title":{"rendered":"AWS RDS : les extensions PostgreSQL"},"content":{"rendered":"\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>

\"\"\u00a0 \u00a0 Les extensions sont ces petits “programmes” qui permettent \u00e0 PostgreSQL d’acqu\u00e9rir de nouvelles fonctionnalit\u00e9s plus pouss\u00e9s via des proc\u00e9dures ou scripts SQL directement charg\u00e9s et ex\u00e9cut\u00e9s en base.<\/p>\n

Voici un nouvel article qui d\u00e9crit les \u00e9tapes n\u00e9cessaires \u00e0 la mise en place d\u2019une extension PostgreSQL pour une instance g\u00e9r\u00e9e dans Amazon RDS pour PostgreSQL.
\nNous prendrons pour exemple l\u2019extension \u00ab\u00a0pg_stat_statements\u00a0\u00bb qui est une extension utilis\u00e9e pour enregistrer les statistiques sur les diff\u00e9rentes requ\u00eates pass\u00e9es en base.<\/p>\n

Cette extension est essentielle pour effectuer des \u00e9tudes de performances au sein d’une instance.<\/p>\n

Nous partirons sur cette extension qui est pr\u00e9sente dans les \u00ab contribs \u00bb par d\u00e9faut sur PostgreSQL, et, qu’Amazon a int\u00e9gr\u00e9 \u00e0 sa solution AWS RDS. Les \u00e9tapes syst\u00e8me de compilations et d\u2019int\u00e9gration\u00a0 pr\u00e9requis sont donc enti\u00e8rement g\u00e9r\u00e9es par AWS.<\/p>\n

 <\/p>\n

Cr\u00e9ation de l\u2019extension dans PostgreSQL<\/h1>\n

On s\u2019assure d\u2019avoir cr\u00e9\u00e9 une base PostgreSQL sous AWS RDS. Nous pouvons prendre une version 11 pour le moteur PostgreSQL. Le nom de notre instance est \u00ab PGcapdata\u00bb.<\/p>\n

\"\"<\/p>\n

A l\u2019aide d\u2019un client PostgreSQL , comme PgAdmin4, nous irons effectuer les op\u00e9rations suivantes.<\/p>\n

Lister les extensions disponibles par d\u00e9faut sous Amazon RDS.<\/p>\n

\"\"<\/p>\n

Il est sera pr\u00e9f\u00e9rable d\u2019effectuer un filtrage sur le nom de l\u2019extension avec \u00a0\u2018pg_%\u2019.<\/p>\n

Voyons si notre extension \u2018pg_stat_statements\u2019 est disponible sous Amazon RDS.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Nous pouvons, d\u2019ores et d\u00e9j\u00e0, cr\u00e9er l\u2019extension<\/p>\n

\"\"<\/p>\n

On v\u00e9rifie sa prise en compte<\/p>\n

\"\"<\/p>\n

 <\/p>\n

La nouvelle extension est donc bien cr\u00e9\u00e9e sous le sch\u00e9ma public de notre base Postgres\u00a0:<\/p>\n

\"\"<\/p>\n

On ira v\u00e9rifier les valeurs configur\u00e9es pour l\u2019extension<\/p>\n

\"\"<\/p>\n

Ces valeurs li\u00e9es \u00e0 l\u2019extension, sont celles par d\u00e9faut d\u00e9finis par Amazon.
\nNous souhaitons, par la suite, changer ces derni\u00e8res.<\/p>\n

Modification des param\u00e8tres<\/h2>\n

S\u2019il l\u2019on souhaite modifier les param\u00e8tres de notre instance PostgreSQL, il sera n\u00e9cessaire de cr\u00e9er un nouveau \u00ab\u00a0parameter group\u00a0\u00bb. Puis effectuer la modification dans ce \u00ab\u00a0parameter group\u00a0\u00bb.<\/p>\n

Cr\u00e9ation du parameter group<\/span><\/strong><\/p>\n

On peut utiliser la console AWS pour cr\u00e9er ce nouveau parameter group.
\nDans Amazon RDS, rep\u00e9rer l\u2019onglet \u00ab \"\" \u00a0\u00bb puis cliquer sur \u00ab Create parameter group \u00bb.<\/p>\n

\"\"<\/p>\n

Puis donner les informations relatives \u00e0 votre nouveau parameter group. On l\u2019appellera \u00ab\u00a0ParamGrouPostgreSQL11PGSTAT\u00a0\u00bb<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Celui-ci est pr\u00e9sent dans la liste des parameter groups.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

awscli<\/span><\/strong><\/p>\n

On peut \u00e9galement utiliser \u2018awscli\u2019 pour cr\u00e9er ce nouveau groupe\u00a0:<\/p>\n

 <\/p>\n

\n
aws rds create-db-parameter-group \\\r\n\u00a0 --db-parameter-group-name ParamGrouPostgreSQL11PGSTAT<\/span> \\\r\n\u00a0 --db-parameter-group-family postgres11 \\\r\n\u00a0 --description \"<\/em>parameter group PostgreSQL with pg_stat_statements<\/span>\"\\\r\n<\/em>  --region eu-west-3<\/pre>\n<\/blockquote>\n
Une fois cr\u00e9\u00e9, il s\u2019agirait d\u2019aller effectuer les modifications n\u00e9cessaires pour les param\u00e8tres de l\u2019instance PostgreSQL, et surtout, pour notre nouvelle extension \u00ab\u00a0pg_stat_statement\u00a0\u00bb.
\nVoici les param\u00e8tres que l\u2019on souhaite appliquer pour cette extension\u00a0:<\/p>\n
pg_stat_statements.max\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0  = 4000<\/em>\r\npg_stat_statements.track\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0  = all\r\npg_stat_statements.track_utility \u00a0= on\r\npg_stat_statements.save\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0  = on\r\ntrack_activity_query_size\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 = 4096<\/em><\/pre>\n
 <\/p>\n
Choisir notre nouveau parameter group et \u00e9diter les valeurs qui seront \u00e0 modifier, on s\u2019aper\u00e7oit dans le champs Values que tout est vide.<\/p>\n
\"\"<\/p>\n
Cliquer sur “Edit parameters” et donner les valeurs comme mentionn\u00e9es au dessus. Ce qui donnera l’affichage suivant:<\/p>\n
\"\"<\/p>\n
 <\/p>\n
awscli<\/span><\/strong><\/p>\n
La commande \u2018awscli\u2019 relative \u00e0 la modification du parameter group est la suivante\u00a0:<\/p>\n
 <\/p>\n
\n
aws rds modify-db-parameter-group \\\r\n \u00a0\u00a0 --db-parameter-group-name ParamGrouPostgreSQL11PGSTAT<\/span> \\\r\n  \u00a0\u00a0--parameters\r\n\u00a0\"ParameterName=pg_stat_statements.max,ParameterValue=4000<\/em><\/span>,ApplyMethod=pending-reboot\" \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\r\n \"ParameterName=pg_stat_statements.track,ParameterValue=ALL<\/em><\/span>,ApplyMethod=immediate<\/em>\" \\\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\r\n \"ParameterName=pg_stat_statements.track_utility,ParameterValue=1<\/em><\/span>,ApplyMethod=immediate<\/em>\" \\\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \r\n\u00a0\"ParameterName=pg_stat_statements.save,ParameterValue=1<\/em><\/span>,ApplyMethod=immediate<\/em>\" \\\r\n\u00a0 \u00a0--region eu-west-3<\/pre>\n<\/blockquote>\n
 <\/p>\n
Attention, le param\u00e8tre \u00ab\u00a0pg_stat_statements.max\u00a0\u00bb est statique. Il ne sera pris en compte qu\u2019apr\u00e8s affectation \u00e0 une instance et reboot de celle-ci.<\/p>\n
Param\u00e9trage instance PostgreSQL<\/h1>\n
 <\/p>\n
La suite consistera \u00e0 attribuer notre nouveau parameter group \u00e0 notre instance PostgreSQL.
\nDans la liste des instances de bases de donn\u00e9es, choisir la base PostgreSQL que l\u2019on souhaite modifier, puis cliquer sur\u00a0\u00a0 \"\"<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Les options \u00e0 modifier se situent dans \u00ab\u00a0Database options\u00a0\u00bb.
\nPrendre le nouveau parameter group<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Puis appliquer les changements en cliquant sur\u00a0 \"\"<\/p>\n
Si cette instance n\u2019est pas en production, on pourra appliquer imm\u00e9diatement les modifications.<\/p>\n
 <\/p>\n
\"\"<\/p>\n
 <\/p>\n
Un reboot de l\u2019instance est n\u00e9cessaire pour prendre en compte ces op\u00e9rations\u00a0:<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Apr\u00e8s reboot, on retournera sur PgAdmin4 v\u00e9rifier nos param\u00e8tres\u00a0:<\/p>\n
\"\"<\/p>\n
 <\/p>\n
awscli<\/span><\/strong><\/p>\n
La commande awscli pour effectuer ce changement est la suivante\u00a0:<\/p>\n
 <\/p>\n
   aws rds modify-db-instance --db-instance-identifier PGcapdata<\/span> \\\r\n      --db-parameter-group-name ParamGrouPostgreSQL11PGSTAT<\/span> \\\r\n      --apply-immediately --region eu-west-3\r\n\r\n<\/pre>\n
Puis red\u00e9marrer l\u2019instance PostgreSQL<\/p>\n
 <\/p>\n
   aws rds reboot-db-instance --db-instance-identifier PGcapdata\r\n\r\n\r\n<\/span><\/pre>\n
La prise en compte de cette nouvelle extension est donc act\u00e9e.<\/p>\n
N’h\u00e9sitez pas \u00e0 laisser vos remarques !<\/p>\n
 <\/p>\n
Emmanuel RAMI<\/p>\n\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"
\u00a0 \u00a0 Les extensions sont ces petits “programmes” qui permettent \u00e0 PostgreSQL d’acqu\u00e9rir de nouvelles fonctionnalit\u00e9s plus pouss\u00e9s via des proc\u00e9dures ou scripts SQL directement charg\u00e9s et ex\u00e9cut\u00e9s en base. Voici un nouvel article qui d\u00e9crit les \u00e9tapes n\u00e9cessaires \u00e0… Continuer la lecture →<\/span><\/a><\/p>\n","protected":false},"author":32,"featured_media":8225,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[295,266],"tags":[],"class_list":["post-8224","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aws","category-postgresql"],"yoast_head":"\nAWS RDS : les extensions PostgreSQL - Capdata TECH 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:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AWS RDS : les extensions PostgreSQL - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"\u00a0 \u00a0 Les extensions sont ces petits “programmes” qui permettent \u00e0 PostgreSQL d’acqu\u00e9rir de nouvelles fonctionnalit\u00e9s plus pouss\u00e9s via des proc\u00e9dures ou scripts SQL directement charg\u00e9s et ex\u00e9cut\u00e9s en base. Voici un nouvel article qui d\u00e9crit les \u00e9tapes n\u00e9cessaires \u00e0… Continuer la lecture →\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2020-01-21T09:49:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-02-26T13:45:48+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2020\/01\/PG_AWS.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"343\" \/>\n\t<meta property=\"og:image:height\" content=\"242\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Emmanuel RAMI\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Emmanuel RAMI\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/\"},\"author\":{\"name\":\"Emmanuel RAMI\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/797b9b6698fa35f7ce3e9a70a8b102ae\"},\"headline\":\"AWS RDS : les extensions PostgreSQL\",\"datePublished\":\"2020-01-21T09:49:11+00:00\",\"dateModified\":\"2021-02-26T13:45:48+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/\"},\"wordCount\":702,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"articleSection\":[\"AWS\",\"PostgreSQL\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/\",\"name\":\"AWS RDS : les extensions PostgreSQL - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2020-01-21T09:49:11+00:00\",\"dateModified\":\"2021-02-26T13:45:48+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"AWS RDS : les extensions PostgreSQL\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.capdata.fr\/#website\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"name\":\"Capdata TECH BLOG\",\"description\":\"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting\",\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.capdata.fr\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.capdata.fr\/#organization\",\"name\":\"Capdata TECH BLOG\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"contentUrl\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"width\":800,\"height\":254,\"caption\":\"Capdata TECH BLOG\"},\"image\":{\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/797b9b6698fa35f7ce3e9a70a8b102ae\",\"name\":\"Emmanuel RAMI\",\"sameAs\":[\"https:\/\/blog.capdata.fr\"],\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/erami\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"AWS RDS : les extensions PostgreSQL - Capdata TECH 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:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/","og_locale":"fr_FR","og_type":"article","og_title":"AWS RDS : les extensions PostgreSQL - Capdata TECH BLOG","og_description":"\u00a0 \u00a0 Les extensions sont ces petits “programmes” qui permettent \u00e0 PostgreSQL d’acqu\u00e9rir de nouvelles fonctionnalit\u00e9s plus pouss\u00e9s via des proc\u00e9dures ou scripts SQL directement charg\u00e9s et ex\u00e9cut\u00e9s en base. Voici un nouvel article qui d\u00e9crit les \u00e9tapes n\u00e9cessaires \u00e0… Continuer la lecture →","og_url":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2020-01-21T09:49:11+00:00","article_modified_time":"2021-02-26T13:45:48+00:00","og_image":[{"width":343,"height":242,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2020\/01\/PG_AWS.jpg","type":"image\/jpeg"}],"author":"Emmanuel RAMI","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Emmanuel RAMI","Dur\u00e9e de lecture estim\u00e9e":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/"},"author":{"name":"Emmanuel RAMI","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/797b9b6698fa35f7ce3e9a70a8b102ae"},"headline":"AWS RDS : les extensions PostgreSQL","datePublished":"2020-01-21T09:49:11+00:00","dateModified":"2021-02-26T13:45:48+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/"},"wordCount":702,"commentCount":0,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"articleSection":["AWS","PostgreSQL"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/","url":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/","name":"AWS RDS : les extensions PostgreSQL - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2020-01-21T09:49:11+00:00","dateModified":"2021-02-26T13:45:48+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/aws-rds-les-extensions-postgresql\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"AWS RDS : les extensions PostgreSQL"}]},{"@type":"WebSite","@id":"https:\/\/blog.capdata.fr\/#website","url":"https:\/\/blog.capdata.fr\/","name":"Capdata TECH BLOG","description":"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting","publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.capdata.fr\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/blog.capdata.fr\/#organization","name":"Capdata TECH BLOG","url":"https:\/\/blog.capdata.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/","url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","contentUrl":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","width":800,"height":254,"caption":"Capdata TECH BLOG"},"image":{"@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/797b9b6698fa35f7ce3e9a70a8b102ae","name":"Emmanuel RAMI","sameAs":["https:\/\/blog.capdata.fr"],"url":"https:\/\/blog.capdata.fr\/index.php\/author\/erami\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8224","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=8224"}],"version-history":[{"count":12,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8224\/revisions"}],"predecessor-version":[{"id":8565,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8224\/revisions\/8565"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/8225"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=8224"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=8224"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=8224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}