jaguar has failed twice in the same spot since the truncate-triggers
patch was committed:

TRUNCATE trunc_trigger_test;
! server closed the connection unexpectedly
! This probably means the server terminated abnormally
! before or while processing the request.
! connection to server was lost

I suppose it is telling us there's some sort of portability issue in
that patch; though I find this pretty surprising because it was mostly
copy-and-paste of well-debugged existing code. Could you get a stack
trace from this crash?

regards, tom lane

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 1 | next ›
Discussion Overview
grouppgsql-hackers @
postedMar 29, '08 at 9:33p
activeMar 29, '08 at 9:33p

1 user in discussion

Tom Lane: 1 post



site design / logo © 2022 Grokbase