{"id":11312,"date":"2018-06-02T10:38:34","date_gmt":"2018-06-02T08:38:34","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/"},"modified":"2023-06-09T16:57:23","modified_gmt":"2023-06-09T14:57:23","slug":"postgresql-11-procedures-are-coming","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/","title":{"rendered":"PostgreSQL 11 : Procedures are coming"},"content":{"rendered":"

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

Reading about new features about future version PostgreSQL 11. I see that procedures will be implemented. Why is it so important? Until now only functions are available in PostgtreSQL. Of course a function is a procedure that returns a value, we can say, yes it\u2019s true but you cannot manage transactions in a function. To better understand let\u2019s do a quick demonstration.
\nNote that I am using the snapshot developer version of PostgreSQL 11 .<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
[postgres@pg_essentials_p1 bin]$ .\/psql<\/code><\/div>\n
Null<\/code> display <\/code>is<\/code> \"NULL\"<\/code>.<\/code><\/div>\n
psql (11devel)<\/code><\/div>\n
Type <\/code>\"help\"<\/code> for<\/code> help.<\/code><\/div>\n
<\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [postgres] > <\/code>select<\/code> version();<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>version<\/code><\/div>\n
--------------------------------------------------------------------------------<\/code><\/div>\n
---------------------------<\/code><\/div>\n
\u00a0<\/code>PostgreSQL 11devel <\/code>on<\/code> x86_64-pc-linux-gnu, compiled <\/code>by<\/code> gcc (GCC) 4.8.5 20150623<\/code><\/div>\n
\u00a0<\/code>(Red Hat 4.8.5-4), 64-<\/code>bit<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [postgres] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

For the demonstration I have a table emp<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
(postgres@[<\/code>local<\/code>]:5432) [test] > <\/code>table<\/code> emp;<\/code><\/div>\n
\u00a0<\/code>id | <\/code>name<\/code><\/div>\n
----+------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | toto<\/code><\/div>\n
\u00a0\u00a0<\/code>2 | Edge<\/code><\/div>\n
(2 <\/code>rows<\/code>)<\/code><\/div>\n
<\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And let\u2019s say I want to insert data in my table using following function<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
CREATE<\/code> or<\/code> replace<\/code> FUNCTION<\/code> fun_insert_emp(id_emp <\/code>int<\/code>,\u00a0 emp_name <\/code>varchar<\/code>(20))<\/code><\/div>\n
\u00a0<\/code>RETURNS<\/code>\u00a0 void <\/code>AS<\/code> $<\/code><\/div>\n
BEGIN<\/code><\/div>\n
\u00a0<\/code>insert<\/code> into<\/code> emp (id,<\/code>name<\/code>) <\/code>values<\/code> (id_emp,emp_name);<\/code><\/div>\n
commit<\/code>;<\/code><\/div>\n
END<\/code>;<\/code><\/div>\n
$<\/code><\/div>\n
LANGUAGE PLPGSQL;<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We can describe the function like this<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n<\/td>\n
\n
\n
(postgres@[<\/code>local<\/code>]:5432) [test] >\u00a0 sf\u00a0 fun_insert_emp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code><\/div>\n
CREATE<\/code> OR<\/code> REPLACE<\/code> FUNCTION<\/code> public<\/code>.fun_insert_emp(id_emp <\/code>integer<\/code>, emp_name <\/code>character<\/code> varying<\/code>)<\/code><\/div>\n
\u00a0<\/code>RETURNS<\/code> void<\/code><\/div>\n
\u00a0<\/code>LANGUAGE plpgsql<\/code><\/div>\n
AS<\/code> $<\/code>function<\/code>$<\/code><\/div>\n
BEGIN<\/code><\/div>\n
\u00a0<\/code>insert<\/code> into<\/code> emp (id,<\/code>name<\/code>) <\/code>values<\/code> (id_emp,emp_name);<\/code><\/div>\n
commit<\/code>;<\/code><\/div>\n
END<\/code>;<\/code><\/div>\n
$<\/code>function<\/code>$<\/code><\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

To call a function we use a select like any built-in function. So let\u2019s try to insert a new employee with the function<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
(postgres@[<\/code>local<\/code>]:5432) [test] > <\/code>select<\/code> fun_insert_emp(3,<\/code>'New Emp'<\/code>);<\/code><\/div>\n
ERROR:\u00a0 invalid <\/code>transaction<\/code> termination<\/code><\/div>\n
CONTEXT:\u00a0 PL\/pgSQL <\/code>function<\/code> fun_insert_emp(<\/code>integer<\/code>,<\/code>character<\/code> varying<\/code>) line 4 <\/code>at<\/code> COMMIT<\/code><\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Seems that the word COMMIT is causing trouble. OK let\u2019s recreate the function without the COMMIT<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
(postgres@[<\/code>local<\/code>]:5432) [test] >\u00a0 sf\u00a0 fun_insert_emp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code><\/div>\n
CREATE<\/code> OR<\/code> REPLACE<\/code> FUNCTION<\/code> public<\/code>.fun_insert_emp(id_emp <\/code>integer<\/code>, emp_name <\/code>character<\/code> varying<\/code>)<\/code><\/div>\n
\u00a0<\/code>RETURNS<\/code> void<\/code><\/div>\n
\u00a0<\/code>LANGUAGE plpgsql<\/code><\/div>\n
AS<\/code> $<\/code>function<\/code>$<\/code><\/div>\n
BEGIN<\/code><\/div>\n
\u00a0<\/code>insert<\/code> into<\/code> emp (id,<\/code>name<\/code>) <\/code>values<\/code> (id_emp,emp_name);<\/code><\/div>\n
END<\/code>;<\/code><\/div>\n
$<\/code>function<\/code>$<\/code><\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And let\u2019s call again the function. We can see that the row was inserted<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n<\/td>\n
\n
\n
(postgres@[<\/code>local<\/code>]:5432) [test] > <\/code>select<\/code> fun_insert_emp(3,<\/code>'New Emp'<\/code>);\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code><\/div>\n
fun_insert_emp<\/code><\/div>\n
----------------<\/code><\/div>\n
<\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] > <\/code>table<\/code> emp;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0 <\/code>name<\/code><\/div>\n
----+---------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | toto<\/code><\/div>\n
\u00a0\u00a0<\/code>2 | Edge<\/code><\/div>\n
\u00a0\u00a0<\/code>3 | New Emp<\/code><\/div>\n
(3 <\/code>rows<\/code>)<\/code><\/div>\n
<\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

But the main problem we saw is that a function in PostgreSQL does not support any transaction instruction (BEGIN\u2026COMMIT, BEGIN\u2026ROLLBACK). This means that in a function I cannot use instructions that allow to rollback or commit based on some conditions.
\nBut PostgreSQL 11 will support procedure. Let\u2019s do again the demonstration with a procedure.
\nLet\u2019s first create the procedure<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
(postgres@[<\/code>local<\/code>]:5432) [test] > <\/code>create<\/code> or<\/code> replace<\/code> procedure<\/code> proc_insert_emp (id_emp <\/code>int<\/code>,\u00a0 emp_name <\/code>varchar<\/code>(20))<\/code><\/div>\n
test-# <\/code>as<\/code> $<\/code><\/div>\n
test$# <\/code>Begin<\/code><\/div>\n
test$# <\/code>insert<\/code> into<\/code> emp (id,<\/code>name<\/code>) <\/code>values<\/code> (id_emp,emp_name);<\/code><\/div>\n
test$# <\/code>commit<\/code>;<\/code><\/div>\n
test$# <\/code>end<\/code> ;<\/code><\/div>\n
test$# $<\/code><\/div>\n
test-# LANGUAGE PLPGSQL;<\/code><\/div>\n
CREATE<\/code> PROCEDURE<\/code><\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And let\u2019s insert a new row in table emp using proc_insert_emp<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n<\/td>\n
\n
\n
(postgres@[<\/code>local<\/code>]:5432) [test] > call\u00a0 proc_insert_emp(4,<\/code>'Brice'<\/code>);<\/code><\/div>\n
CALL<\/code><\/div>\n
<\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] > <\/code>table<\/code> emp;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0 <\/code>name<\/code><\/div>\n
----+---------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | toto<\/code><\/div>\n
\u00a0\u00a0<\/code>2 | Edge<\/code><\/div>\n
\u00a0\u00a0<\/code>3 | New Emp<\/code><\/div>\n
\u00a0\u00a0<\/code>4 | Brice<\/code><\/div>\n
(4 <\/code>rows<\/code>)<\/code><\/div>\n
<\/div>\n
(postgres@[<\/code>local<\/code>]:5432) [test] ><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We can see that the row was inserted. But the main difference is the support of autonomous transaction and this will be definitively change life for developers.<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Reading about new features about future version PostgreSQL 11. I see that procedures will be implemented. Why is it so important? Until now only functions are available in PostgtreSQL. Of course a function is a procedure that returns a value, we can say, yes it\u2019s true but you cannot manage transactions in […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[1369],"type_dbi":[],"class_list":["post-11312","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-procedures-postgresql-11"],"acf":[],"yoast_head":"\nPostgreSQL 11 : Procedures are coming - dbi Blog<\/title>\n<meta name=\"description\" content=\"postgresql 11, procedures\" \/>\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-11-procedures-are-coming\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 11 : Procedures are coming\" \/>\n<meta property=\"og:description\" content=\"postgresql 11, procedures\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-06-02T08:38:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-09T14:57:23+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"PostgreSQL 11 : Procedures are coming\",\"datePublished\":\"2018-06-02T08:38:34+00:00\",\"dateModified\":\"2023-06-09T14:57:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/\"},\"wordCount\":270,\"commentCount\":0,\"keywords\":[\"Procedures postgresql 11\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/\",\"name\":\"PostgreSQL 11 : Procedures are coming - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-06-02T08:38:34+00:00\",\"dateModified\":\"2023-06-09T14:57:23+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"postgresql 11, procedures\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 11 : Procedures are coming\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL 11 : Procedures are coming - dbi Blog","description":"postgresql 11, procedures","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-11-procedures-are-coming\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 11 : Procedures are coming","og_description":"postgresql 11, procedures","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/","og_site_name":"dbi Blog","article_published_time":"2018-06-02T08:38:34+00:00","article_modified_time":"2023-06-09T14:57:23+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"PostgreSQL 11 : Procedures are coming","datePublished":"2018-06-02T08:38:34+00:00","dateModified":"2023-06-09T14:57:23+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/"},"wordCount":270,"commentCount":0,"keywords":["Procedures postgresql 11"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/","name":"PostgreSQL 11 : Procedures are coming - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-06-02T08:38:34+00:00","dateModified":"2023-06-09T14:57:23+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"postgresql 11, procedures","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-11-procedures-are-coming\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 11 : Procedures are coming"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11312","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=11312"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11312\/revisions"}],"predecessor-version":[{"id":25769,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11312\/revisions\/25769"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11312"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11312"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11312"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=11312"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}