Re: server closed connection on a select query

From: Guillaume Lelarge <guillaume(dot)lelarge(at)gmail(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: server closed connection on a select query
Date: 2005-11-22 17:42:55
Message-ID: d854adec0511220942u76aa977ay@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sorry for this late answer. I tried a lot of things and it still doesn't work.

2005/11/11, Martijn van Oosterhout <kleptog(at)svana(dot)org>:
> On Thu, Nov 10, 2005 at 11:53:04PM +0100, Guillaume LELARGE wrote:
> > Hi,
> >
> > I've installed a 8.1.0 PostgreSQL server on a SCO OpenServer 5.0.6. It
> > seemed to work well with psql and such tools. I tried to connect to
> > this server with pgAdmin3 and a query failed. I tried to find which
> > part of the query was wrong and I have a strange result :
> >
> > SELECT 1 FROM pg_language WHERE lanispl IS TRUE;
> > this one crashes the server.
> >
> > SELECT 1 FROM pg_language WHERE lanispl = true;
> > works.
>
> Does this pass regression testing (ie make check)? It looks like it's
> dying all over the please. Posting a backtrace (bt in gdb) would be
> more helpful.
>

Some tests failed.. strangely, it seems int4 and int8 share the same
range. I didn't go further on this because I don't think this will
resolve my real issue.

See my next answer to Larry for more informations.

--
Guillaume.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2005-11-22 17:52:39 Re: Practical error logging for very large COPY
Previous Message Tom Lane 2005-11-22 17:16:00 Re: Practical error logging for very large COPY