| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PANIC: heap_update_redo: no block |
| Date: | 2006-03-22 03:56:02 |
| Message-ID: | 9709.1142999762@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> 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.
That was probably Vadim's original reasoning for not being very verbose
in the redo routines' various PANIC messages. But for failures in the
field it'd be awfully nice to be able to see this info from a standard
build, so I'm thinking we should improve the elog messages. If you feel
like creating a patch I'll be glad to apply it ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken Winter | 2006-03-22 04:00:33 | Confused about a function returning SETOF |
| Previous Message | surabhi.ahuja | 2006-03-22 03:53:57 | partial resultset in java |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-22 04:31:43 | Re: Poor performance o |
| Previous Message | Aftab Alam | 2006-03-22 03:40:17 | unsubscribe |