Thread: Regression fails on Alpha True64 V5.0 for yesterdays cvs

The interval test fails with the following msg:
--- 216,222 ----
   -- known to change the allowed input syntax for type interval without
   -- updating pg_aggregate.agginitval
   select avg(f1) from interval_tbl;
! server closed the connection unexpectedly
!       This probably means the server terminated abnormally
!       before or while processing the request.
! connection to server was lost

No core file and I don't know which of the many error messages in
postmaster.log are normal and which are not.
I've run the tests with debug enabled, and I see no further output
after
DEBUG:  query: select avg(f1) from interval_tbl;
I can find no matching "DEBUG:  parse tree: { QUERY " output.
It works as expected on x86 linux and QNX4.

PS: I posted an earlier version of this message to pgsql-hackers, but
it was stalled, as I am not subscribed to that list.

--
Bernd Tegge                  mailto:tegge@repas-aeg.de
Tel: ++49-511-87449-12       repas AEG Automation GmbH
Fax: ++49-511-87449-20       GS Hannover, Germany

"Tegge, Bernd" <tegge@repas-aeg.de> writes:
> The interval test fails with the following msg:
> --- 216,222 ----
>    -- known to change the allowed input syntax for type interval without
>    -- updating pg_aggregate.agginitval
>    select avg(f1) from interval_tbl;
> ! server closed the connection unexpectedly

This is bad :-(

I tried to reproduce the problem on the Alpha available at
SourceForge's compile farm.  No luck --- regression tests run
perfectly there, at least with vanilla configuration (I used
"configure --enable-cassert").  So it doesn't seem hardware-
specific, but perhaps it depends on the OS.

> No core file and I don't know which of the many error messages in
> postmaster.log are normal and which are not.
> I've run the tests with debug enabled, and I see no further output
> after
> DEBUG:  query: select avg(f1) from interval_tbl;

Is there not even a report of the backend crashing?  If the postmaster
did not log a child-exit message then there's something more than a
plain old backend crash here.

            regards, tom lane