On Thu, Sep 10, 2015 at 1:08 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> On Thu, Sep 10, 2015 at 9:29 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
>>
>> On Thu, Sep 10, 2015 at 12:49 PM, Amit Kapila <amit.kapil...@gmail.com>
>> wrote:
>> > On Wed, Sep 9, 2015 at 6:43 PM, Fujii Masao <masao.fu...@gmail.com>
>> > wrote:
>> >>
>> >> On Fri, Sep 4, 2015 at 4:48 PM, Amit Kapila <amit.kapil...@gmail.com>
>> >> wrote:
>> >>
>> >
>> > - errdetail("Could not rename \"%s\" to \"%s\": %m.",
>> > + errdetail("\"%s\" could not be renamed to \"%s\": %m.",
>> >
>> > Is there any reason to change this message?
>> > I think you have changed this message to make it somewhat similar with
>> > the new message we are planning to use in this function, but I don't see
>> > that as compelling reason to change this message.
>>
>> The following part in error message style guide made me feel that's
>> better.
>> IOW, I didn't think that the previous message follows complete-sentence
>> style.
>>
>> -------------------------
>> Detail and hint messages: Use complete sentences, and end each with a
>> period.
>> -------------------------
>>
>
> I am not sure if this indicates that previous used message was wrong.
> If we look for errdetail in code, then there are many other similar
> messages.Yes, but the existence of other similar messages doesn't mean that they follow the style. We need to understand what "complete sentence" means. I was thinking that "complete sentence" basically needs to contain the subject. But to be honest I'm not confident about that. Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
