On Thu, Apr 16, 2015 at 3:25 PM, Heikki Linnakangas <hlinnaka@iki.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
