Re: error report on slru.c - Mailing list pgsql-patches

From Gaetano Mendola
Subject Re: error report on slru.c
Date
Msg-id 41608DC8.2050300@bigfoot.com
Whole thread Raw
In response to Re: error report on slru.c  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
>
>>Tom Lane wrote:
>>
>>>This violates the message style guidelines, IMHO.
>
>
>>My first impression is that it should be swapped.  The error is that the
>>file could not be opened.  The detail is that the files is related to
>>transaction status information.
>
>
> No, the error is that the transaction status couldn't be accessed.  The
> fact that it is stored in a file is implementation detail, and primary
> messages should not focus on implementation detail.

Right, so the only way a DBA have is to look the details! Is there another
way to know the file and the offset a transaction belong to ?



Regards
Gaetano Mendola



pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: error report on slru.c
Next
From: Neil Conway
Date:
Subject: pgcrypto: make const array static