Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iCPQC-0000OY-Gt for pgsql-admin@arkaria.postgresql.org; Mon, 23 Sep 2019 14:34:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iCPQB-0000B7-Cw for pgsql-admin@arkaria.postgresql.org; Mon, 23 Sep 2019 14:34:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iCPQA-0000B0-QT for pgsql-admin@lists.postgresql.org; Mon, 23 Sep 2019 14:34:35 +0000 Received: from sonic307-2.consmr.mail.bf2.yahoo.com ([74.6.134.41]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iCPQ3-0003yw-2V for pgsql-admin@lists.postgresql.org; Mon, 23 Sep 2019 14:34:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1569249264; bh=Hg5GvmPOQXMc7Y4V1EJLvD847m+2dvmnQPr9VN62nHA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=P8pEFvmHWcPid74pEi3Br090cditRY9rXh7T8A8rwNrmkXC5il/lP02iyc/7Hmmjtb8KQQKwK9iyDZ7TfuQo+03+Gw2L/vNC0dJOCBCFYH5J9ha2nCJ1/2CkvRnPpyemRVV2eq+pxmMH3jvw70NkITJ6fCAR4SnKVCIRb6NzT6lrDXG7uwNRkPA/gU3v6E24Gq3QtBH3jFaAfBh7Glna1Trj+0kDPw2UlQ9ZGYlunYfKkIsiKvfhXjqWhVRJ+z82RMT/prNZnnWYq713LpXdf87702LkoQG0shQ77/iRYSJDNGmOTZeLALHwdruerl+uVncwLt9YW+pYVyq7LGqxbQ== X-YMail-OSG: b4CcttQVM1kAgvv7kBSQ08Icxnw7pHkPBvcyy.yjbjwyVx9kQ0fg3GHAEcQCoSs yQzsCqmaQ4BbruE2yv9ZBX8b51S7pOW7MPP7Qc53uP9kojeLvJqjiukBX0y4_0PK4h7HzjKLuLl6 MhW.D0uoeTp5NXn..BZQYTZm8Gyg6_vkAdI6IimG2jwtu_hHXaKU1LwEHJmtBsQbDopiGQUm9Cq1 5hR4qdMxo_QQYPKlANC6hDmaXVNblGxyzUKIkLvUIHVxPD68Ht4YIDqSXt0tXbyabWXx2BWqry9F b6ujnCuXvaDOrm.kt7sNrURoPEgayNPQGEzY8sLwC_DSTYp.1HtKZa5esT3YhL8NKOCv_bdlc.pL 0b87ARAlKhqvciyGLen3bYHUhN0JAAMck6mX.iyN.6lxXLYAJIGq8o86sJF08yXfsqfafdro_DiV efPGaNXP0gqseyul4TJ2VzuXYVvrxMxI0GNNclkXmM5eLdVxKE0jVDwoCwMKqARECnmFdePgTdDe KMyQuPGhhayo3M_Iq0eVyum1E.vR_6WAFvWz__Q6PqSHaUJad4sn4mWYp1a23jDXEpEJyZcBgnfp Nr_FtisQG1WwBjVCgMAtFz6EEOab7DVocA4qEmwgso30n42_L1.hzYi3TgV4Zo.DfzMAY4bbOoht .tpawzYlBX8TUu6nSjXwIRBsgwFkUr3kcqdIocH.zQftBiDLYEg4kGB9n3NX04qenFV44R4.XMyQ Uy0XYGsCnk8t5a_4i_SlceKPRO8PVJQglCdYlNU4kSzTYq_lOBxbPBoq.d2nu2sRatQmDK72EEjH 8bI7co_i6_1yL3uXX.J42N4NcRVho473Q4ATmVKGNkqrU9o3vtjmma3RP3M7uNmv_Ce9IL.UK1ee dl4fNavOuGr.P6wPYDFVtkJK7MQWaqD7pqw9pa.dTcjXKxO0sLTEjAx._Cg0RmfJ_xjt6h3JtRyh YpCc9p_ThZioJ6WpJEhWPdEVuy5HFfWWv0BjN7BK_LzWSMBAu.ayz9xi3aOXAbEx80ugamDNwJCz 4Gj71F14kkZ7I4us9gNtjC1mjAEeEUxMVVLsiNcXGpQUwbK4ltxSuYShVCVgGzCpwfYt5nQ_t5.U KXTD4EjjTGZtUXRAL5tI1rRWfzWFIeDMCRDWP_ll8EnZJ1ttdhmEYe6oqneOkgN1d_baVkPkm3xP QskgNLgEx0ov5O1n5JqlyjrOmpUUEZZwjDZrODTdsb26POtDhgtxGWtD9H34jlbs_DEwnO7SBL6V uN533h5.mBZfnBU6M8K4H5SFf2.DVAGUnGIPHoBLeEybZ_xJnS7Yue3sD_JXJjUueQha6 Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.bf2.yahoo.com with HTTP; Mon, 23 Sep 2019 14:34:24 +0000 Date: Mon, 23 Sep 2019 14:34:23 +0000 (UTC) From: Pepe TD Vo Reply-To: Pepe TD Vo To: Morris de Oryx Cc: Pgsql-admin Message-ID: <647259260.7679971.1569249263294@mail.yahoo.com> In-Reply-To: References: <290131249.7032562.1568999216076.ref@mail.yahoo.com> <290131249.7032562.1568999216076@mail.yahoo.com> <567497570.7112630.1569015183464@mail.yahoo.com> <343266304.7137386.1569017757225@mail.yahoo.com> Subject: Re: Merge statement MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7679970_1334696123.1569249263286" X-Mailer: WebService/1.1.14303 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36 Content-Length: 9530 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_7679970_1334696123.1569249263286 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable good morning, happy Monday. fyi, I upgraded postgres in AWS to 11.1 and the merge function for procedur= e is still not working. Still complained the same error that:=C2=A0ERROR:= =C2=A0 "ecisdrdm.application_cdim" is not a known variableLINE 14: MERGE IN= TO ecisdrdm.application_cdim prod=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^SQL state: 42601Character: 348 v/r, Bach-Nga No one in this world is pure and perfect.=C2=A0 If you avoid people for the= ir mistakes you will be alone. So judge less, love and forgive more.To call= him a dog hardly seems to do him justice though in as much as he had four = legs, a tail, and barked, I admit he was, to all outward appearances. But t= o those who knew him well, he was a perfect gentleman (Hermione Gingold) **Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely = rich *** Faithful talent *** Sharing success=20 On Sunday, September 22, 2019, 10:36:01 PM EDT, Morris de Oryx wrote: =20 =20 Postgres has had stored functions for ages, but only added stored procedur= es in version 11. Historically, you'll see people calling stored functions = in Postgres "stored procedures" as that's what other folks call them. It di= dn't matter because Postgres only had the one thing. For what's new in Post= gres 11 stored procedures, here's a place to look: https://severalnines.com/database-blog/overview-new-stored-procedures-postg= resql-11 The change you're referring to is that a stored procedure (but not a functi= on) has the ability to manage its own transaction blocks. I actually have no clue...I've only read about the new stored procedures. B= ut if you're coming from Oracle, you're likely looking for PG 11 stored pro= cedures, at least some of the time. =20 =20 =20 ------=_Part_7679970_1334696123.1569249263286 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
good morning, happy Monday.

fyi, I upgraded postgres in AWS to 11.1 and the merge function for pro= cedure is still not working. Still complained the same error that: 
ERROR:  "ecisdrdm.= application_cdim" is not a known variable
LINE 14: MERGE INTO eci= sdrdm.application_cdim prod
          &n= bsp;         ^
SQL state: 42601
Cha= racter: 348

v/r,

Bach-Nga

No one in this world is pure and perfect.  If you avoid people = for their mistakes you will be alone. So judge less, love and forgive more.=
To call him a dog hardly seems to do hi= m justice though in as much as he had four legs, a tail, and barked, I admi= t he was, to all outward appearances. But to those who knew him well, he wa= s a perfect gentleman (Hermione Gingold)

**Live simply **Love generously **Care deepl= y **Speak kindly.
*** Genuinely rich *** Fa= ithful talent *** Sharing success


=20
=20
On Sunday, September 22, 2019, 10:36:01 PM EDT, Morris = de Oryx <morrisdeoryx@gmail.com> wrote:


Postgres has had stored functions for ages, but only added = stored procedures in version 11. Historically, you'll see people calling st= ored functions in Postgres "stored procedures" as that's what other folks c= all them. It didn't matter because Postgres only had the one thing. For wha= t's new in Postgres 11 stored procedures, here's a place to look:


The change you're referring to is that a stored pro= cedure (but not a function) has the ability to manage its own transaction b= locks.

I actually have no clue...I'= ve only read about the new stored procedures. But if you're coming from Ora= cle, you're likely looking for PG 11 stored procedures, at least some of th= e time.
------=_Part_7679970_1334696123.1569249263286--