Re: bad logging around broken restore_command - Mailing list pgsql-hackers

From David Steele
Subject Re: bad logging around broken restore_command
Date
Msg-id f7abecee-c532-4b29-2bd9-d32758a8f970@pgmasters.net
Whole thread Raw
In response to Re: bad logging around broken restore_command  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
Hi Jeff,

On 2/6/20 9:23 AM, Fujii Masao wrote:
> 
>> I've attached a patch which emits a LOG message for ENOENT.
> 
> Isn't it better to use "could not stat file" message even in ENOENT case?
> If yes, something like message that you used in the patch should be
> logged as DETAIL or HINT message. So, what about the attached patch?

What do you think of Fujii's changes?

Regards,
-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Bert Scalzo
Date:
Subject: New feature request: Query Rewrite Cache
Next
From: David Steele
Date:
Subject: Re: POC: rational number type (fractions)