Re: strange failure in plpgsql_control tests (on fulmar, ICC 14.0.3)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange failure in plpgsql_control tests (on fulmar, ICC 14.0.3)
Date: 2018-03-17 14:32:48
Message-ID: 13435.1521297168@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> I happened to be updating our machine running our buildfarm animals, and
> I noticed something quite strange - the machine was unexpectedly running
> out of disk space, which is rather suspicious as it's running just the
> regression tests :-/

> After a bit of investigation, I found this:
> Right - the plpgsql_control.out output has about 58GB, which is somewhat
> excessive I guess. The reason is fairly simple:

> NOTICE: 2147483620..2147483647 by 10: i = 2147483620
> NOTICE: 2147483620..2147483647 by 10: i = 2147483630
> NOTICE: 2147483620..2147483647 by 10: i = 2147483640
> NOTICE: 2147483620..2147483647 by 10: i = -2147483646
> NOTICE: 2147483620..2147483647 by 10: i = -2147483636
> NOTICE: 2147483620..2147483647 by 10: i = -2147483626
> ... many more NOTICE messages ...

> Looking at the plpgsql_call.out timestamp, this seems to be running
> since January 1, which also correlates with the last results reported to
> pgbuildfarm.

Ouch. That test is in fact new as of 31 Dec, and what this seems to
prove is that plpgsql's handling of loop-variable overflow doesn't
work on fulmar.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-03-17 14:55:21 Re: strange failure in plpgsql_control tests (on fulmar, ICC 14.0.3)
Previous Message Peter Eisentraut 2018-03-17 14:18:11 Re: disable SSL compression?