Re: Calling ROUND w/o a numeric cast blowing up all connections (9.1) - Mailing list pgsql-general

From Tom Lane
Subject Re: Calling ROUND w/o a numeric cast blowing up all connections (9.1)
Date
Msg-id 28631.1360372392@sss.pgh.pa.us
Whole thread Raw
In response to Calling ROUND w/o a numeric cast blowing up all connections (9.1)  (Wells Oliver <wellsoliver@gmail.com>)
Responses Re: Calling ROUND w/o a numeric cast blowing up all connections (9.1)
List pgsql-general
Wells Oliver <wellsoliver@gmail.com> writes:
> I don't know why this is happening, but it's infuriating. From the psql
> prompt:

> mydb=# select round(5/2, 1);
> SSL SYSCALL error: EOF detected

Huh.  Works for me ...

> Nothing shows up in the log.

Either your logging is broken or you're looking in the wrong log, I
think, because that sure looks like a backend crash.  And the postmaster
would certainly bleat about a backend crash.

> Have I broken my cast function? My round function? Have I angered the RDMS
> gods? Can anyone give me any pointers?

Dunno, have you messed around with either casting or round()?  Can you
reproduce this in a freshly-created database?

FWIW, a stock database ought to have these versions of round():

postgres=# \df round
                          List of functions
   Schema   | Name  | Result data type | Argument data types |  Type
------------+-------+------------------+---------------------+--------
 pg_catalog | round | double precision | double precision    | normal
 pg_catalog | round | numeric          | numeric             | normal
 pg_catalog | round | numeric          | numeric, integer    | normal
(3 rows)


            regards, tom lane

pgsql-general by date:

Previous
From: Wells Oliver
Date:
Subject: Calling ROUND w/o a numeric cast blowing up all connections (9.1)
Next
From: Wells Oliver
Date:
Subject: Re: Calling ROUND w/o a numeric cast blowing up all connections (9.1)