[check_postgres] Existing active checks, upgrading version, PGSQL9+ compat

[Greg Sabino Mullane]

On Fri, Dec 28, 2012 at 12:26:04PM -0500, Greg Sabino Mullane wrote:
> On Fri, Dec 28, 2012 at 09:24:29AM +0100, Guillaume Lelarge wrote:
> ...
> > > ERROR: ERROR: function pg_size_pretty(integer) is not unique
> > > 
> > 
> > I'm a bit puzzled by this one. Is it still against a PostgreSQL 9.2
> > server? does it happen with other releases?
> 
> This was the recent ill-advised change to have a pg_size_pretty that 
> takes a bigint, and another to take numeric. Which means simple queries 
> that worked before now fail. I will fix it (one the check_postgres 
> side: hopefully they will fix on the Postgres side too!)

Hm....I don't see any calls to pg_size_pretty that are not using 
another function (pg_database_size or pg_relation_size) that already 
returns a bigint. Perhaps see if you can duplicate the problem 
on the git head version?

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://mail.endcrypt.com/pipermail/check_postgres/attachments/20121228/da7e7b8b/attachment.sig>