Re: Using nulls with earthdistance operator crashes backend

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Using nulls with earthdistance operator crashes backend
Дата
Msg-id 200109061611.f86GBUS28974@candle.pha.pa.us
обсуждение исходный текст
Ответ на Using nulls with earthdistance operator crashes backend  (Mark Stosberg <mark@summersault.com>)
Список 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@postgresql.org so that your
> message can get through to the mailing list cleanly
>

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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Build problem with CVS version
Следующее
От: Tom Lane
Дата:
Сообщение: Re: ILIKE + OR fault - propably a memory leak