Re: pg_connect dumps core

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matthias Teege <matthias(at)mteege(dot)de>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: pg_connect dumps core
Date: 2001-03-04 16:31:40
Message-ID: 9431.983723500@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Matthias Teege <matthias(at)mteege(dot)de> writes:
> tclsh8.3
> % load libpgtcl.so
> % pg_connect m3
> Connection to database failed
> FATAL 1: Database "m3" does not exist in the system catalog.
> % pg_connect m2
> Segmentation fault (core dumped)

> in postgresql errlog there are:

> FATAL 1: Database "m3" does not exist in the system catalog.
> pq_recvbuf: unexpected EOF on client connection

Strange. Evidently it's getting as far as opening the connection
(pq_recvbuf is used in the backend, not the postmaster), but then
crashing after that. I can't see any reason why it would work for
pgaccess but not for you. (I notice that pgaccess uses the conninfo
style of arguments to pg_connect, but that shouldn't make a
difference...)

Can you provide a stack backtrace from the core file?

regards, tom lane

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Peter Eisentraut 2001-03-04 19:07:24 Re: Merging PyGreSQL development into PostgreSQL
Previous Message Matthias Teege 2001-03-04 13:34:57 pg_connect dumps core