From: | Neil Darlow <ndarlow(at)csi(dot)com> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | libpgtcl core dump with socket access. |
Date: | 1998-09-27 10:34:03 |
Message-ID: | 360E149B.245ECE2E@csi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hi,
My environment is Red Hat 5.1 Intel, kernel 2.0.35-2, glibc-2.0.7 running
PostgreSQL-6.3.2 and Tcl/Tk-8.0.2. Colleagues have reported that the problem
does not occur with the original *stock* Red Hat 5.1 distribution.
If you connect to a database locally with: set dbc [pg_connect "dbname"]
then there is no problem. Executing: set result [pg_exec $dbc "select * from
non_existent_table"]
results in an error message being reported by tclsh or wish.
If you connect to a database with: set dbc [pg_connect -conninfo
"dbname=database
host=hostname port=portname user=username password=password"]
then execute: set result [pg_exec $dbc "select * from non_existent_table"]
always results in a core dump.
I have checked other libpgtcl interface commands and they appear to work ok. It
just seems to be pg_exec over socket connections. Performing the same operations
with psql always results in error messages being returned.
Has anyone else noticed this problem? Is there a solution?
Neil Darlow (UK).
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Heller | 1998-09-27 17:22:14 | Creating a database with JDBC |
Previous Message | Debbie and Mike Meyer | 1998-09-26 19:23:49 | Re: [INTERFACES] SLOWNESS ON JDBC INTERFACE |