Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D9CC59FCD7D for ; Thu, 25 Oct 2007 13:03:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 57096-01 for ; Thu, 25 Oct 2007 13:03:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B5D4E9FCC79 for ; Thu, 25 Oct 2007 12:59:44 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9PFxYCD016980; Thu, 25 Oct 2007 11:59:34 -0400 (EDT) To: Craig McElroy cc: PostgreSQL Admin List , Teodor Sigaev Subject: Re: Problem with PITR Past Particular WAL File In-reply-to: <1FAEADD9-FE4A-444E-9B45-D6192B0265E5@contegix.com> References: <10123.1193250394@sss.pgh.pa.us> <1FAEADD9-FE4A-444E-9B45-D6192B0265E5@contegix.com> Comments: In-reply-to Craig McElroy message dated "Thu, 25 Oct 2007 02:34:35 -0500" Date: Thu, 25 Oct 2007 11:59:34 -0400 Message-ID: <16979.1193327974@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/254 X-Sequence-Number: 27168 Craig McElroy writes: > Core was generated by `/usr/local/pgsql/bin/postgres -D /pgdata01/data'. > Program terminated with signal 11, Segmentation fault. > #0 0x080b8ee0 in entrySplitPage () > #1 0x080baccf in ginInsertValue () > #2 0x080b81b7 in gin_xlog_cleanup () > #3 0x080af4ce in StartupXLOG () > #4 0x080c04ca in BootstrapMain () > #5 0x08186b2f in StartChildProcess () > #6 0x081889eb in PostmasterMain () > #7 0x0814ee9e in main () Hm, I wonder if this is explained by a bug already fixed in 8.2.5: 2007-06-04 11:59 teodor * src/backend/access/gin/: gindatapage.c, ginentrypage.c, ginget.c, ginvacuum.c, ginxlog.c (REL8_2_STABLE): Fix bundle bugs of GIN: - Fix possible deadlock between UPDATE and VACUUM queries. Bug never was observed in 8.2, but it still exist there. HEAD is more sensitive to bug after recent "ring" of buffer improvements. - Fix WAL creation: if parent page is stored as is after split then incomplete split isn't removed during replay. This happens rather rare, only on large tables with a lot of updates/inserts. - Fix WAL replay: there was wrong test of XLR_BKP_BLOCK_* for left page after deletion of page. That causes wrong rightlink field: it pointed to deleted page. - add checking of match of clearing incomplete split - cleanup incomplete split list after proceeding All of this chages doesn't change on-disk storage, so backpatch... But second point may be an issue for replaying logs from previous version. Teodor, can you comment on whether this stack trace looks like it could be related to that fix? Craig, can you retry your test scenario on 8.2.5? regards, tom lane