In 9.1:

regression=# select pg_size_pretty(8*1024*1024);
 pg_size_pretty 
----------------
 8192 kB
(1 row)

In HEAD:

regression=# select pg_size_pretty(8*1024*1024);
ERROR:  function pg_size_pretty(integer) is not unique
LINE 1: select pg_size_pretty(8*1024*1024);
               ^
HINT:  Could not choose a best candidate function. You might need to add explicit type casts.

The argument for adding pg_size_pretty(numeric) was pretty darn thin in
the first place, IMHO; it does not seem to me that it justified this
loss of usability.

			regards, tom lane

Responses

• Re: No, pg_size_pretty(numeric) was not such a hot idea at 2012-05-26 04:45:35 from Fujii Masao

pgsql-hackers by date

Next:	From: Jeff Frost	Date: 2012-05-26 00:32:05
	Subject: Re: Backends stalled in 'startup' state: index corruption
Previous:	From: Robert Haas	Date: 2012-05-25 23:42:05
	Subject: Re: heap metapages