Re: Using nulls with earthdistance operator crashes backend

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Mark Stosberg <mark(at)summersault(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Using nulls with earthdistance operator crashes backend
Date: 2001-09-06 16:11:30
Message-ID: 200109061611.f86GBUS28974@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

This will be fixed in 7.2:

test=> select null <@> '1,1'::point;
?column?
----------

(1 row)

>
> 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/
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-09-06 16:47:54 Re: ILIKE + OR fault - propably a memory leak
Previous Message Stephan Szabo 2001-09-06 15:48:31 Re: Bug #440: trigger can not find a function