Re: PANIC: heap_update_redo: no block
От | Alex bahdushka |
---|---|
Тема | Re: PANIC: heap_update_redo: no block |
Дата | |
Msg-id | [email protected] обсуждение исходный текст |
Ответ на | Re: PANIC: heap_update_redo: no block ("Qingqing Zhou" <[email protected]>) |
Ответы |
Re: PANIC: heap_update_redo: no block
|
Список | pgsql-general |
On 3/21/06, Qingqing Zhou <[email protected]> wrote: > > "Tom Lane" <[email protected]> wrote > > > > While at it, you should extend the error message to include the relation > > ID, so you have some idea which table is affected ... this is certainly > > not a very informative message ... > > > > Exactly. Please use the following version: > > - elog(PANIC, "heap_update_redo: no block"); > + elog(PANIC, "heap_update_redo: no block: target blcknum: %u, > relation(%u/%u/%u) length: %u", > + ItemPointerGetBlockNumber(&(xlrec->target.tid)), > + reln->rd_node.spcNode, > + reln->rd_node.dbNode, > + reln->rd_node.relNode, > + RelationGetNumberOfBlocks(reln)); > > BTW: I just realized that there is another (better) way to do so is to > enable WAL_DEBUG in xlog.h and SET XLOG_DEBUG=true. And that's why we don't > have much error message in xlog redo. > Hrm ok ill see about doing either the patch or setting wal_debug to true (or both). However im currently on vacation till Saturday so ill do this first thing then and report the results back. Thank you very much! > Regards, > Qingqing > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings >
В списке pgsql-general по дате отправления: