Re: BUG #19394: error in ecpg

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "alex(at)ilona(dot)su" <alex(at)ilona(dot)su>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19394: error in ecpg
Date: 2026-02-05 15:31:40
Message-ID: CAKFQuwZ=wv1xpuQANkes3V_iyocfjqaxwOXza4Ym=NoHJePj3Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thursday, February 5, 2026, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 19394
> Logged by: Alexey G
> Email address: alex(at)ilona(dot)su
> PostgreSQL version: Unsupported/Unknown
> Operating system: linux
> Description:
>
> I have database 4duksh on 182.168.123.4. Postgresq 13.
>
> If i set
> EXEC SQL CONNECT TO 4duksh(at)192(dot)168(dot)123(dot)4 AS con1 USER postgres;
> i get error near "4"
>
> If i set
> EXEC SQL CONNECT TO db4duksh(at)192(dot)168(dot)123(dot)4 AS con1 USER postgres;
> as well
>
>
This is not a bug. The options and limitations for writing the target are
documented here.

https://www.postgresql.org/docs/current/ecpg-connect.html#ECPG-CONNECTING

In PostgreSQL, plain identifiers cannot begin with a number.

https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS

Apparently target is a bit looser in what it allows since I’d have expected
both to require quoting.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2026-02-05 16:52:50 Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
Previous Message Laurenz Albe 2026-02-05 14:58:50 Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists