Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id EF3B39F937C for ; Thu, 25 Oct 2007 15:05:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 51165-09 for ; Thu, 25 Oct 2007 15:05:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from hook.sigaev.ru (nbtest.sai.msu.ru [212.192.243.50]) by postgresql.org (Postfix) with ESMTP id 8A2F19F949A for ; Thu, 25 Oct 2007 15:05:53 -0300 (ADT) Received: by hook.sigaev.ru (Postfix, from userid 1003) id 4CBD9398E9; Thu, 25 Oct 2007 22:05:51 +0400 (MSD) Received: from xor.sai.msu.ru (xor.sai.msu.ru [212.192.243.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hook.sigaev.ru (Postfix) with ESMTP id 4DBE8398E5; Thu, 25 Oct 2007 22:05:45 +0400 (MSD) Message-ID: <4720DAF9.6080002@sigaev.ru> Date: Thu, 25 Oct 2007 22:05:45 +0400 From: Teodor Sigaev User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.6) Gecko/20070813 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Tom Lane CC: Craig McElroy , PostgreSQL Admin List Subject: Re: Problem with PITR Past Particular WAL File References: <10123.1193250394@sss.pgh.pa.us> <1FAEADD9-FE4A-444E-9B45-D6192B0265E5@contegix.com> <16979.1193327974@sss.pgh.pa.us> In-Reply-To: <16979.1193327974@sss.pgh.pa.us> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/255 X-Sequence-Number: 27169 >> #0 0x080b8ee0 in entrySplitPage () >> #1 0x080baccf in ginInsertValue () Corrupted stack? gin_xlog_cleanup() doesn't call ginInsertValue() directly. >> #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 () > Teodor, can you comment on whether this stack trace looks like it could > be related to that fix? No, I suppose. That changes was about deadlock prevention, recognize splits and fixes in deletion of page in a posting tree. entrySplitPage() is a split of page of indexed values. Hmm. I suppose, I found a reason. Real backtrace should look like: gin_xlog_cleanup() ginContinueSplit() prepareEntryScan(,,,NULL) // makes btree.ginstate = NULL ginInsertValue() entrySplitPage() // tries to access // btree->ginstate->tupdesc in // 497 line That piece of code: value = index_getattr(leftrightmost, FirstOffsetNumber, btree->ginstate->tupdesc, &isnull); btree->entry = GinFormTuple(btree->ginstate, value, NULL, 0); ItemPointerSet(&(btree->entry)->t_tid, BufferGetBlockNumber(lbuf), InvalidOffsetNumber); It just makes new tuple with the same value and another ItemPointer. Some later I'll make a patch which will not call index_getattr() and GinFormTuple() - now I know how make a test suite. -- Teodor Sigaev E-mail: teodor@sigaev.ru WWW: http://www.sigaev.ru/