From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Adams <dpadams@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: psql 14.7/15.2 report a bogus syntax error on function and
 procedure files that use BEGIN ATOMIC
In-reply-to: 
 <CAPXPcQu8bUcJ3gJ3L_htXiPDpMZPh78+jncNhi+ypyiOKoxhog@mail.gmail.com>
References: 
 <CAPXPcQuSEWTCqVnoiVALpkdAM_HXXdAf8kYm0WYF8Z2htX6v-A@mail.gmail.com>
 <1666633.1678682081@sss.pgh.pa.us>
 <CAPXPcQu8bUcJ3gJ3L_htXiPDpMZPh78+jncNhi+ypyiOKoxhog@mail.gmail.com>
Comments: In-reply-to David Adams <dpadams@gmail.com>
	message dated "Mon, 13 Mar 2023 15:49:26 +1100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1669792.1678683562.1@sss.pgh.pa.us>
Date: Mon, 13 Mar 2023 00:59:22 -0400
Message-ID: <1669793.1678683562@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1669793.1678683562%40sss.pgh.pa.us>
Precedence: bulk

David Adams <dpadams@gmail.com> writes:
> As far as I know, the problem only shows up with reading in a file with -f
> or <: That's a bit different to entering the lines one by one.

No joy on that either ...

$ cat test.sql 
CREATE OR REPLACE FUNCTION tell_me_how_atomic()
RETURNS text
LANGUAGE SQL
BEGIN ATOMIC
return 'atomic';
END;
$ psql -f test.sql
CREATE FUNCTION
$ cat test.sql | psql
CREATE FUNCTION

> I've checked again, and can't find any gremlins/invisible characters in the
> source file, attached. And, this only happens with scripts that use BEGIN
> ATOMIC, and it seems to happen on all of those files.

Are you entirely sure you're using a new-enough psql?  I can replicate
your symptom if I try to use v13 psql to send this command to a
v14-or-later server.

			regards, tom lane