On 3/30/07, ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> wrote:
>
> Attached is an updated DSM patch. I've left the core function of DSM only
> and dropped other complicated features in this release.
>
>
I was testing this patch when got this server crash. The patch is applied
on the current CVS HEAD. I thought you would be interested in this.

The patch worked for smaller scaling factor and its reproducible.

Test: pgbench -s 90 -i -F 95 postgres

Stack:

(gdb) bt
#0 0x001d37a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00213955 in raise () from /lib/tls/libc.so.6
#2 0x00215319 in abort () from /lib/tls/libc.so.6
#3 0x082dc04f in ExceptionalCondition (conditionName=0x83a7ad7 "!(victim)",
errorType=0x83a7622 "FailedAssertion",
fileName=0x83a7487 "deadspace.c", lineNumber=1080) at assert.c:51
#4 0x0821eb29 in dsm_create_chunk (dsmrel=0xb7bcd744, key=0xbff589c0) at
deadspace.c:1080
#5 0x0821d473 in dsm_record_state (rnode=0xaee02698, pageno=98304,
state=DSM_LOW) at deadspace.c:333
#6 0x0821d29e in DegradeDeadSpaceState (rel=0xaee02698, buffer=10645) at
deadspace.c:254
#7 0x0817b542 in lazy_scan_heap (onerel=0xaee02698, vacrelstats=0x9f5f2e0,
Irel=0x9f5f4dc, nindexes=1, iter=0x9f5f57c)
at vacuumlazy.c:586
#8 0x0817a733 in lazy_vacuum_rel (onerel=0xaee02698, vacstmt=0x9f39c94) at
vacuumlazy.c:209
#9 0x08174e5c in vacuum_rel (relid=16388, vacstmt=0x9f39c94,
expected_relkind=114 'r') at vacuum.c:1107
#10 0x0817421c in vacuum (vacstmt=0x9f39c94, relids=0x0, isTopLevel=1
'\001') at vacuum.c:401
#11 0x0823d90b in ProcessUtility (parsetree=0x9f39c94, queryString=0x9f62f94
"vacuum analyze", params=0x0,
isTopLevel=1 '\001', dest=0x9f39cf0, completionTag=0xbff5a040 "") at
utility.c:929
#12 0x0823bdd6 in PortalRunUtility (portal=0x9f60f8c, utilityStmt=0x9f39c94,
isTopLevel=1 '\001', dest=0x9f39cf0,
completionTag=0xbff5a040 "") at pquery.c:1170
#13 0x0823bf0a in PortalRunMulti (portal=0x9f60f8c, isTopLevel=1 '\001',
dest=0x9f39cf0, altdest=0x9f39cf0,
completionTag=0xbff5a040 "") at pquery.c:1262
#14 0x0823b6df in PortalRun (portal=0x9f60f8c, count=2147483647,
isTopLevel=1 '\001', dest=0x9f39cf0, altdest=0x9f39cf0,
completionTag=0xbff5a040 "") at pquery.c:809
#15 0x082365df in exec_simple_query (query_string=0x9f399d4 "vacuum
analyze") at postgres.c:956
#16 0x08239e43 in PostgresMain (argc=4, argv=0x9ecfc94, username=0x9ecfc64
"perf") at postgres.c:3503
#17 0x08204e84 in BackendRun (port=0x9ee3628) at postmaster.c:2987
#18 0x08204493 in BackendStartup (port=0x9ee3628) at postmaster.c:2614
#19 0x0820228b in ServerLoop () at postmaster.c:1214
#20 0x08201c66 in PostmasterMain (argc=3, argv=0x9ecdc50) at postmaster.c
:967
#21 0x081a9e0b in main (argc=3, argv=0x9ecdc50) at main.c:188


--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com

Thank you for reporting!

I noticed that I need more examination the case when dsm relations or
dsm chunks are exhausted. I'll do more tests for DSM.


"Pavan Deolasee" <pavan.deolasee@gmail.com> wrote:

> I was testing this patch when got this server crash. The patch is applied
> on the current CVS HEAD. I thought you would be interested in this.
>
> The patch worked for smaller scaling factor and its reproducible.
>
> Test: pgbench -s 90 -i -F 95 postgres
>
> #3 0x082dc04f in ExceptionalCondition (conditionName=0x83a7ad7 "!(victim)",
> errorType=0x83a7622 "FailedAssertion",
> fileName=0x83a7487 "deadspace.c", lineNumber=1080) at assert.c:51

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly