From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron <ronljohnsonjr@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: query can't merge into table of the other schema
In-reply-to: <c56d9a46-be49-eac3-f3c3-efd76240aea6@gmail.com>
References: <1425722754.312953.1541603425493.ref@mail.yahoo.com>
 <1425722754.312953.1541603425493@mail.yahoo.com>
 <c56d9a46-be49-eac3-f3c3-efd76240aea6@gmail.com>
Comments: In-reply-to Ron <ronljohnsonjr@gmail.com>
	message dated "Wed, 07 Nov 2018 16:22:19 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <12035.1541630162.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Wed, 07 Nov 2018 17:36:02 -0500
Message-ID: <12036.1541630162@sss.pgh.pa.us>
Precedence: bulk

Ron <ronljohnsonjr@gmail.com> writes:
> On 11/07/2018 09:10 AM, Pepe TD Vo wrote:
>> *ERROR: "cidrdba.sc_date_in" is not a known variable*

> That doesn't look like a "can't merge table from another schema" error.

>> *LINE 13:    MERGE INTO cidrdba.sc_date_in prod*
>> *               ^*
>> *SQL state: 42601*
>> *Character: 352*

> What happens when you run the statement through psql?

It will fail, of course, since there's no MERGE statement in Postgres.

I think the reason for the weird error is that the plpgsql scanner is
seeing the "INTO cidrdba.sc_date_in" part and trying to process that
as an "INTO plpgsql-variable" clause, before it's fed the rest of the
statement to the core parser, which is what would notice that MERGE
isn't a known command.  Maybe we could improve matters by reordering
that processing, but it might be a lot of work for a small benefit.

			regards, tom lane