| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | hlinnaka(at)iki(dot)fi |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: show xl_prev in xlog.c errcontext |
| Date: | 2015-04-16 06:36:04 |
| Message-ID: | CAB7nPqT8jSd9QfEyk2MLb7nwLMD+=KPazdKrgJ+7fb-fZ+MndQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 16, 2015 at 3:25 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> On 04/15/2015 11:35 PM, Alvaro Herrera wrote:
>>
>> I found this patch in my local repo that I wrote some weeks or months
>> ago while debugging some XLog corruption problem: it was difficult to
>> pinpoint what XLog record in a long sequence of WAL files was causing a
>> problem, and the displaying the prev pointer in errcontext made finding
>> it much easier -- I could correlate it with pg_xlogdump output, I think.
>
>
> Seems like a good idea, but why print the prev pointer, and not the location
> of the record itself?
And both?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-04-16 06:46:32 | Supporting src/test/modules in MSVC builds |
| Previous Message | Heikki Linnakangas | 2015-04-16 06:25:37 | Re: show xl_prev in xlog.c errcontext |