Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running

Ok, here are the results of the assertion TRAP (mind you, same error on the
same line, but a different machine than the original)


database log:

TRAP: FailedAssertion("!(((ntp)->t_data)->t_infomask & 0x0010)", File:
"catcache.c", Line: 1729)


gdb:

Program received signal SIGABRT, Aborted.
0x40109ac1 in kill () from /lib/libc.so.6
(gdb) where
#0  0x40109ac1 in kill () from /lib/libc.so.6
#1  0x401096eb in raise () from /lib/libc.so.6
#2  0x4010b127 in abort () from /lib/libc.so.6
#3  0x08208036 in ExceptionalCondition (conditionName=0x40212d24 "8,\023",
errorType=0x6 <Address 0x6 out of bounds>, fileName=0x0, lineNumber=1729)
    at assert.c:51
#4  0x081ff88f in build_dummy_tuple (cache=0x41469048, nkeys=1,
skeys=0xbfffe410) at catcache.c:1735
#5  0x081fe917 in SearchCatCache (cache=0x41469048, v1=0, v2=0, v3=0, v4=0) at
catcache.c:1240
#6  0x08173908 in pgstat_vacuum_tabstat () at pgstat.c:817
#7  0x081156d9 in vacuum (vacstmt=0x8342b5c) at vacuum.c:272
#8  0x0819f7cc in PortalRunUtility (portal=0x835bf2c, query=0x8342bb8,
dest=0x8342a3c, completionTag=0xbfffebd0 "") at pquery.c:934
#9  0x0819fb01 in PortalRunMulti (portal=0x835bf2c, dest=0x8342a3c,
altdest=0x8342a3c, completionTag=0xbfffebd0 "") at pquery.c:1001
#10 0x0819f174 in PortalRun (portal=0x835bf2c, count=2147483647,
dest=0x8342a3c, altdest=0x8342a3c, completionTag=0xbfffebd0 "") at
pquery.c:617
#11 0x0819b760 in exec_simple_query (query_string=0x8342824 "vacuum full
analyse ean_available") at postgres.c:933
#12 0x0819dce0 in PostgresMain (argc=4, argv=0x8308b04, username=0x8308adc
"vugtf") at postgres.c:2986
#13 0x08171f31 in BackendRun (port=0x83177f0) at postmaster.c:2817
#14 0x08171991 in BackendStartup (port=0x83177f0) at postmaster.c:2453
#15 0x0816ff6f in ServerLoop () at postmaster.c:1198
#16 0x0816f4a3 in PostmasterMain (argc=3, argv=0x8307788) at postmaster.c:917
#17 0x0813d22d in main (argc=3, argv=0x8307788) at main.c:268
#18 0x400f5d06 in __libc_start_main () from /lib/libc.so.6


Obviously, continuing was not an option ;)



--
Best,




Frank.