reopen 503294
reopen 503403
tag 503294 +pending
tag 503403 +pending
thanks
Hi Andreas,
On Sonntag, 16. August 2009, Andreas Olsson wrote:
> As of munin 1.2.6-13 the plugin postgres_space_ yet again has
> "capabilities=autoconf..." set. I am assuming this happend while fixing
> this bug? Hence I'
Sorry, kind of got the wrong link pasted in there. I actually intended
refering to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503294
// Andreas
signature.asc
Description: This is a digitally signed message part.
As of munin 1.2.6-13 the plugin postgres_space_ yet again has
"capabilities=autoconf..." set. I am assuming this happend while fixing this
bug? Hence I'm wondering if that's an intentional change back, or merely
something which happend by mistake?
There reason I'm wondering is that that capabi
tag 518790 pending
tag 518790 fixed-upstream
thanks
Hello Kurt, hello *,
thanks for your report!
> It seems there are 3 problems with the space stats for postgresql:
> - I get alot of "Use of uninitiliased value in addition" for lines
> 178 and 175.
I inserted some checks for the uninitialized
On Sun, Mar 08, 2009 at 08:24:11PM +0100, Kurt Roeckx wrote:
> The uninitialized warnings seem to come from the query
> with the SUM() in it. For some reason it does not
> seem to like queries with aggregates in it. I've tried
> casting it to integer and varchar and things like that,
> but that d
The uninitialized warnings seem to come from the query
with the SUM() in it. For some reason it does not
seem to like queries with aggregates in it. I've tried
casting it to integer and varchar and things like that,
but that doesn't solve anything.
The same warnings are in the postgres_block_rea
Package: munin-node
Version: 1.2.6-8~bpo40+1
Hi,
It seems there are 3 problems with the space stats for postgresql:
- I get alot of "Use of uninitiliased value in addition" for lines
178 and 175.
- The list of tables (@names) does not seem to contain any normal
table. I only get tables from
7 matches
Mail list logo
