Request a Demo
Home   >   mailing lists

Re: BUG #19394: error in ecpg - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #19394: error in ecpg
Date
Msg-id CAKFQuwZ=wv1xpuQANkes3V_iyocfjqaxwOXza4Ym=NoHJePj3Q@mail.gmail.com
Whole thread
In response to BUG #19394: error in ecpg  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Tree view
On Thursday, February 5, 2026, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      19394
Logged by:          Alexey G
Email address:      alex@ilona.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@192.168.123.4 AS con1 USER postgres;
i get error near "4"

If i set
EXEC SQL CONNECT TO db4duksh@192.168.123.4 AS con1 USER postgres;
as well


This is not a bug.  The options and limitations for writing the target are documented here.


In PostgreSQL, plain identifiers cannot begin with a number.


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

David J.


pgsql-bugs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
Next
From: Laurenz Albe
Date:
Subject: Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists