To: pgsql-admin@postgresql.org
From: George Neuner <gneuner2@comcast.net>
Subject: Re: Merge statement
Message-ID: <7a6db92e-0ddc-89e8-7f7e-dae04ddad6bd@comcast.net>
Date: Tue, 24 Sep 2019 12:31:53 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------07E24FF0B6E84902B233B1BC"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------07E24FF0B6E84902B233B1BC
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On Mon, 23 Sep 2019 15:48:06 +0000 (UTC), Pepe TD Vo <pepevo@yahoo.com> 
wrote:

 >Yes, I heard  MERGE is not a command in Postgres but the others said
 >merge statement added stored procedures in version 11
 >
 >I upgraded my postgresql from 10.6 to 11.1. in AWS, still not work.
 >thank you,
 >Bach-Nga

You misunderstood.

Postrgesql added stored procedures in version 11.  Unlike stored 
/functions/ (which PG has had forever), stored procedures allow 
transactions within their code. This is similar to the stored procedures 
in Oracle and it helps with Oracle -> Postgresql conversions.

However, Postgresql does NOT and never did have a MERGE command. The 
"documentation" page you discovered was just a proposal for an 
implementation that never happened.

Postgresql can detect conflicts on INSERT and perform an UPDATE instead 
(see https://www.postgresql.org/docs/current/sql-insert.html).  This is 
not exactly the same as Oracle's MERGE so you'll have to study it 
carefully to make you understand the nuances and be sure it works as 
intended in your application ... but it is the closest you can get using 
Postgresql.

George

--------------07E24FF0B6E84902B233B1BC
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On Mon, 23 Sep 2019 15:48:06 +0000 (UTC), Pepe TD Vo
    <a class="moz-txt-link-rfc2396E" href="mailto:pepevo@yahoo.com">&lt;pepevo@yahoo.com&gt;</a> wrote:<br>
    <br>
    &gt;Yes, I heard  MERGE is not a command in Postgres but the others
    said<br>
    &gt;merge statement added stored procedures in version 11<br>
    &gt;<br>
    &gt;I upgraded my postgresql from 10.6 to 11.1. in AWS, still not
    work.<br>
    &gt;thank you,<br>
    &gt;Bach-Nga<br>
    <br>
    You misunderstood.<br>
    <br>
    Postrgesql added stored procedures in version 11.  Unlike stored <i>functions</i>
    (which PG has had forever), stored procedures allow transactions
    within their code. This is similar to the stored procedures in
    Oracle and it helps with Oracle -&gt; Postgresql conversions.<br>
    <br>
    However, Postgresql does NOT and never did have a MERGE command. 
    The "documentation" page you discovered was just a proposal for an
    implementation that never happened.<br>
    <br>
    Postgresql can detect conflicts on INSERT and perform an UPDATE
    instead (see 
    <a class="moz-txt-link-freetext" href="https://www.postgresql.org/docs/current/sql-insert.html">https://www.postgresql.org/docs/current/sql-insert.html</a>).  This is
    not exactly the same as Oracle's MERGE so you'll have to study it
    carefully to make you understand the nuances and be sure it works as
    intended in your application ... but it is the closest you can get
    using Postgresql.<br>
    <br>
    George
  </body>
</html>

--------------07E24FF0B6E84902B233B1BC--