Menu
▾
▴
Re: [Postgres-xc-general] segfault while adding delete datanode
|
From: muayad y <mua...@ya...> - 2015-09-12 04:08:02
|
Hi,postgres-xc-1.2.1
dbg:
Program received signal SIGSEGV, Segmentation fault.0x00000000004b3fd4 in heap_update (relation=0x2af74668f6c8, otid=0x91ae61b4, newtup=0xffffffff91ae62f8, cid=0, crosscheck=0x0, wait=1 '\001', hufd=0x7fffaff71640, lockmode=0x7fffaff7163c) at heapam.c:30123012 newtup->t_tableOid = RelationGetRelid(relation);
(gdb) info args followed by print for each address relation = 0x2af74668f6c8= > $44 = 47241526572744otid = 0x91ae61b4 => p otid => $45 = (ItemPointer) 0x91ae61b4 => p 0x91ae61b4 =>$46 = 2444124596newtup = 0xffffffff91ae62f8 p=> $47 = 18446744071858709240cid = 0crosscheck = 0x0wait = 1 '\001'hufd = 0x7fffaff71640 => $48 = 140736145593920lockmode = 0x7fffaff7163c => $49 = 140736145593916
(gdb) info localsresult = HeapTupleMayBeUpdatedxid = 67601hot_attrs = 0x91ae6518key_attrs = 0x1e4f3c8lp = 0x2af73e072fb0oldtup = {t_len = 72, t_self = {ip_blkid = {bi_hi = 0, bi_lo = 0}, ip_posid = 7}, t_tableOid = 9001, t_xc_node_id = 108, t_data = 0x2af73e074d70}heaptup = 0x7fffaff715f0page = 0x2af73e072f80 ""block = 0mxact_status = MultiXactStatusForKeySharebuffer = 78newbuf = 52vmbuffer = 0vmbuffer_new = 0need_toast = 0 '\000'already_marked = 0 '\000'newtupsize = 29939120pagefree = 8have_tuple_lock = 0 '\000'iscombo = 0 '\000'satisfies_hot = 0 '\000'satisfies_key = 0 '\000'
use_hot_update = 0 '\000'key_intact = 0 '\000'all_visible_cleared = 0 '\000'all_visible_cleared_new = 0 '\000'checked_lockers = -27 '\345'locker_remains = 83 'S'xmax_new_tuple = 0xmax_old_tuple = 0infomask_old_tuple = 0infomask2_old_tuple = 10999infomask_new_tuple = 18024infomask2_new_tuple = 63992__func__ = "heap_update"
ThanksMU
On Thursday, September 10, 2015 9:53 PM, 鈴木 幸市 <ko...@in...> wrote:
Maybe some internal variable value got bigger than the limit. Could you analyze the core to find where segfault happened (i.e. the variable value which caused the segfault)? Also, could you let me know the version of XC you used.
Thank you very much;
---Koichi SuzukiNTT DATA Intellilink Cor...@in...
2015/09/11 9:12、muayad y <mua...@ya...> のメール：
Add/delete node works fine when table has ~ 9million rows, but segfault in heap_update when table gets bigger, any idea help ? thanks in advance
Core was generated by `postgres: pgxl test [local] ALTER TABLE '.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004949f0 in heap_update ()
(gdb) bt
#0 0x00000000004949f0 in heap_update ()
#1 0x0000000000495f12 in simple_heap_update ()
#2 0x00000000004fd3c0 in PgxcClassAlter ()
#3 0x00000000005763c8 in ATExecCmd ()
#4 0x0000000000578d56 in ATController ()
#5 0x000000000068ab1d in ProcessUtilitySlow.isra.8 ()
#6 0x0000000000688dc8 in standard_ProcessUtility ()
#7 0x0000000000685a07 in PortalRunUtility ()
#8 0x000000000068668d in PortalRunMulti ()
#9 0x0000000000687272 in PortalRun ()
#10 0x0000000000684970 in PostgresMain ()
#11 0x000000000046d1f9 in ServerLoop ()
#12 0x00000000006429d6 in PostmasterMain ()
#13 0x000000000046da8d in main ()
(gdb)
table info:
CREATE TABLE sbtest (id int NOT NULL, k int NOT NULL DEFAULT '0', c char(120) NOT NULL DEFAULT '', pad char(60) NOT NULL DEFAULT '', PRIMARY KEY (id)) DISTRIBUTE BY hash(id);
user limits:
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 3101645
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 131072
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 3101645
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Thanks
MU
------------------------------------------------------------------------------
_______________________________________________
Postgres-xc-general mailing list
Pos...@li...
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
|
