1
0
mirror of https://github.com/postgres/postgres.git synced 2025-06-14 18:42:34 +03:00

Mark the float8 -> int8 cast as implicit. This resolves the problem

pointed out by Barry Lind: UPDATE bigintcol = 10000000000 fails because
the constant is initially taken as float8.  We really need a better way,
but it's not gonna happen for 7.3.

Also, remove int4reltime() function, which is redundant with the
existing binary-compatibility coercion path from int4 to reltime,
and probably has been unreachable code for a long while.
This commit is contained in:
Tom Lane
2002-09-01 00:58:07 +00:00
parent 845a6c3acc
commit 3c49c4b152
4 changed files with 22 additions and 24 deletions

View File

@ -9,7 +9,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/utils/adt/nabstime.c,v 1.96 2002/08/04 06:44:47 thomas Exp $
* $Header: /cvsroot/pgsql/src/backend/utils/adt/nabstime.c,v 1.97 2002/09/01 00:58:06 tgl Exp $
*
* NOTES
*
@ -1735,15 +1735,6 @@ istinterval(char *i_string,
*
*****************************************************************************/
Datum
int4reltime(PG_FUNCTION_ARGS)
{
int32 timevalue = PG_GETARG_INT32(0);
/* Just coerce it directly to RelativeTime ... */
PG_RETURN_RELATIVETIME((RelativeTime) timevalue);
}
/*
* timeofday -
* returns the current time as a text. similar to timenow() but returns