Re: Tom Lane 2011-04-03 1397.1301782...@sss.pgh.pa.us
Yeah, that's clearly a bug --- fix committed, thanks for the patch!
It could explain Devrim's report if the parameters passed by psql had
some problem that was detectable by conninfo_array_parse(). That seems
a bit unlikely, but I did
Christoph Berg c...@df7cb.de writes:
I'm still seeing that problem: 9.1 HEAD compiled in my $HOME, with
Debian's 9.0.1-2 libpq5 in /usr/lib:
$ LC_ALL=C bin/psql
psql: connection pointer is NULL
Upgrading to libpq5 9.0.4-1 makes things a bit better:
$ LC_ALL=C bin/psql
psql: invalid
On Sat, 2011-04-02 at 18:10 -0400, Tom Lane wrote:
It could explain Devrim's report if the parameters passed by psql had
some problem that was detectable by conninfo_array_parse(). That
seems a bit unlikely, but I did think of one possibility: if Devrim
was
testing 9.1 psql with a 9.0
I'm getting the following message after upgrading to Alpha5 on my Fedora
14 box:
$ psql -p 5433
psql: connection pointer is NULL
which comes from libpq. Server is running, and I can connect it to via
9.0's psql.
This is a regular RPM build. Am I doing something wrong, or?
Regards,
--
Devrim
2011/4/2 Devrim GÜNDÜZ dev...@gunduz.org:
I'm getting the following message after upgrading to Alpha5 on my Fedora
14 box:
$ psql -p 5433
psql: connection pointer is NULL
which comes from libpq. Server is running, and I can connect it to via
9.0's psql.
This is a regular RPM build. Am I
Joseph Adams joeyadams3.14...@gmail.com writes:
I couldn't reproduce this (using upstream source on Ubuntu). However,
I did find a little bug in libpq causing the connection handle to
become NULL in the event of an option parsing error. This bug has
been around since release 9.0.0, and may
