On Tue, Jul 26, 2022 at 10:23 AM Peter Smith <smithpb2250@gmail.com> wrote:
>
> On Tue, Jul 26, 2022 at 2:09 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> >
> > I am not really sure how much we gain by maintaining consistency with
> > slot_name because if due to this we have to change the error messages
> > as well then it can create an inconsistency with reserved origin
> > names. Consider message: DETAIL: Origin names "any", "none", and
> > names starting with "pg_" are reserved. Now, if we change this to
> > "ANY", "NONE" in the above message, it will look a bit odd as "pg_"
> > starts with lower case letters.
> >
>
> Sure, the message looks a bit odd with the quotes like you wrote
> above, but I would not suggest to change it that way - I was thinking
> more like below (which is similar to the style the slot_name messages
> use)
>
> CURRENT
> DETAIL: Origin names "any", "none", and names starting with "pg_" are reserved.
>
> SUGGESTED
> DETAIL: Origin names ANY, NONE, and names starting with "pg_" are reserved.
>
I see your point but not sure if that is an improvement over the
current one, so, let's wait and see if we get some other votes in
favor of your suggestion.
--
With Regards,
Amit Kapila.