Re: Redundant errdetail prefix "The error was:" in some logical replication messages - Mailing list pgsql-hackers

From Peter Smith
Subject Re: Redundant errdetail prefix "The error was:" in some logical replication messages
Date
Msg-id CAHut+PufG363HNvgV8=zfjedKKu6zoJT3v7rHr8ME_sWiWqkOw@mail.gmail.com
Whole thread Raw
In response to Re: Redundant errdetail prefix "The error was:" in some logical replication messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Redundant errdetail prefix "The error was:" in some logical replication messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Mar 30, 2021 at 5:10 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Peter Smith <smithpb2250@gmail.com> writes:
> > There are a couple of error messages within the logical replication
> > code where the errdetail text includes a prefix of "The error was:"
>
> Hmm, isn't project style more usually to include the error reason
> in the primary message?  That is,
>
>              ereport(LOG,
> -                    (errmsg("could not drop the replication slot \"%s\" on publisher",
> -                            slotname),
> -                     errdetail("The error was: %s", res->err)));
> +                    (errmsg("could not drop the replication slot \"%s\" on publisher: %s",
> +                            slotname, res->err)));
>
> and so on.  If we had reason to think that res->err would be extremely
> long, maybe pushing it to errdetail would be sensible, but I'm not
> seeing that that is likely.
>
> (I think the "the" before "replication slot" could go away, too.)

Thanks for the review and advice.

PSA version 2 of this patch which adopts your suggestions.

------
Kind Regards,
Peter Smith.
Fujitsu Australia

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: wal stats questions
Next
From: Amit Kapila
Date:
Subject: Re: [PATCH] Provide more information to filter_prepare