| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | alex(at)ilona(dot)su |
| Subject: | BUG #19394: error in ecpg |
| Date: | 2026-02-05 14:58:42 |
| Message-ID: | 19394-0997a5bdb836c074@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Nitin Motiani | 2026-02-05 10:05:26 | Re: BUG #19379: Role pg_read_all_data don't allowed read large objects |