Re: Improve error reporting for few options in pg_createsubscriber

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Improve error reporting for few options in pg_createsubscriber
Date: 2025-04-04 04:41:24
Message-ID: CALDaNm26TqzK8jcOmMbFJruh7JHFnVcGAtNju3DCyj3844OFeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 4 Apr 2025 at 09:36, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> A few comments:
> *
> pg_createsubscriber.exe -D ..\..\data_standby -d db1 -d db2 -d db1
> --publication pub1 --publication pub1 -P "dbname=postgres port=5432"
> -p 5444 --dry-run
> pg_createsubscriber: error: database "db1" specified more than once
> for --database
>
> Even when user has used short form, we are displaying long form for
> database. I suggest to use both short and long form where applicable.

Fixed this.

> *
> "invalid object type \"%s\" specified for --remove". Isn't it better
> to use the short form as well in this error message?

Fixed this.

The attached v2 version patch has the changes for the same.

Regards,
Vignesh

Attachment Content-Type Size
v2-0001-Improve-error-reporting-consistency-in-pg_creates.patch text/x-patch 4.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-04-04 05:01:04 Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits
Previous Message Fujii Masao 2025-04-04 04:38:50 Re: Some codes refer slot()->{'slot_name'} but it is not defined