Re: "pgoutput" options missing on documentation

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: emre(at)hasegeli(dot)com
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "pgoutput" options missing on documentation
Date: 2023-12-18 03:30:25
Message-ID: CAA4eK1K8P9S5gVy_uf6-AdUA+sPpmfneaF+d=u_FBE=woHh4HA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 15, 2023 at 7:06 PM Emre Hasegeli <emre(at)hasegeli(dot)com> wrote:
>
> > I saw that the original "publication_names" error was using
> > errcode(ERRCODE_INVALID_PARAMETER_VALUE), but TBH since there is no
> > option given at all I felt ERRCODE_SYNTAX_ERROR might be more
> > appropriate errcode for those 2 mandatory option errors.
>
> It makes sense to me. Changed.
>

I found the existing error code appropriate because for syntax
specification, either we need to mandate this at the grammar level or
at the API level. Also, I think we should give a message similar to an
existing message: "publication_names parameter missing". For example,
we can say, "proto_version parameter missing". BTW, I also don't like
the other changes parse_output_parameters() done in 0001, if we want
to improve all the similar messages there are other places in the code
as well, so we can separately make the case for the same.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-12-18 04:27:49 Re: "pgoutput" options missing on documentation
Previous Message torikoshia 2023-12-18 02:41:42 Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)