Using nulls with earthdistance operator crashes backend - Mailing list pgsql-bugs

From Mark Stosberg
Subject Using nulls with earthdistance operator crashes backend
Date
Msg-id 20010731095840.A94094-100000@nollie.summersault.com
Whole thread Raw
Responses Re: Using nulls with earthdistance operator crashes backend  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Using nulls with earthdistance operator crashes backend  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
Hello!

Here's now to reproduce my bug:
* Start with Postgres 7.1.2
(specifically:  PostgreSQL 7.1 on i386--freebsd4.3, compiled by GCC 2.95.3
)
* Install earthdistance operator from the contrib directory.
* try this:
cascade=> select null <@> '1,1'::point;

## The result I get:
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

###############

I expected simply for "null" to be returned as the result. I can work
around
this by including an extra step to make sure that my data is not null
before
it's passed off a SQL statement like this.

  Thanks!

   -mark

http://mark.stosberg.com/

pgsql-bugs by date:

Previous
From: "Dong, Meng"
Date:
Subject: RE: 'order by' and 'desc' not working in subquery using 'not in'
Next
From: Stephan Szabo
Date:
Subject: Re: 'order by' and 'desc' not working in subquery using 'not in'