Re: A doubt about a newly added errdetail
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: amit.kapila16@gmail.com
Cc: alvherre@alvh.no-ip.org, houzj.fnst@fujitsu.com,
pgsql-hackers@lists.postgresql.org
Date: 2022-09-28T09:22:32Z
Lists: pgsql-hackers
At Wed, 28 Sep 2022 13:47:25 +0530, Amit Kapila <amit.kapila16@gmail.com> wrote in
> On Wed, Sep 28, 2022 at 11:30 AM Kyotaro Horiguchi
> <horikyota.ntt@gmail.com> wrote:
> > I'm fine with that. By the way, related to the area, I found the
> > following error messages.
> >
> > > errmsg("publication \"%s\" is defined as FOR ALL TABLES",
> > > NameStr(pubform->pubname)),
> > > errdetail("Schemas cannot be added to or dropped from FOR ALL TABLES publications.")));
> >
> > It looks tome that the errmsg and errordetail are reversed. Isn't the following order common?
> >
> > > errmsg("schemas cannot be added to or dropped from publication \"%s\".",
> > > NameStr(pubform->pubname)),
> > > errdetail("The publication is defined as FOR ALL TABLES.")));
> >
>
> This one seems to be matching with the below existing message:
> ereport(ERROR,
> (errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE),
> errmsg("publication \"%s\" is defined as FOR ALL TABLES",
> NameStr(pubform->pubname)),
> errdetail("Tables cannot be added to or dropped from FOR ALL TABLES
> publications.")));
Yeah, so I meant that I'd like to propose to chage the both. I just
wanted to ask people whether that proposal is reasonable or not.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
Commits
-
Remove publicationcmds.c's expr_allowed_in_node as a function
- d0b1dbcb9845 16.0 landed
- a60b11327bbd 15.0 landed
-
Improve some publication-related error messages
- f5441b912493 15.0 landed
- 4148c8b3daf9 16.0 landed