Re: attndims, typndims still not enforced, but make the value within a sane threshold - Mailing list pgsql-hackers

From Junwang Zhao
Subject Re: attndims, typndims still not enforced, but make the value within a sane threshold
Date
Msg-id CAEG8a3JB8yegJU4y0vE-_1Va_-MtVvKsM8_Q+d7iR8mPAj-GJw@mail.gmail.com
Whole thread Raw
In response to Re: attndims, typndims still not enforced, but make the value within a sane threshold  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi Tom and Michael,

On Fri, Sep 20, 2024 at 12:38 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Michael Paquier <michael@paquier.xyz> writes:
> > On Fri, Sep 20, 2024 at 11:51:49AM +0800, Junwang Zhao wrote:
> >> Should you also bump the catalog version?
>
> > No need to worry about that when sending a patch because committers
> > take care of that when merging a patch into the tree.  Doing that in
> > each patch submitted just creates more conflicts and work for patch
> > authors because they'd need to recolve conflicts each time a
> > catversion bump happens.  And that can happen on a daily basis
> > sometimes depending on what is committed.
>
> Right.  Sometimes the committer forgets to do that :-(, which is
> not great but it's not normally a big problem either.  We've concluded
> it's better to err in that direction than impose additional work
> on patch submitters.
>
> If you feel concerned about the point, best practice is to include a
> mention that catversion bump is needed in your draft commit message.
>
>                         regards, tom lane

Got it, thanks for both of your explanations.

--
Regards
Junwang Zhao



pgsql-hackers by date:

Previous
From: Mats Kindahl
Date:
Subject: Re: Use streaming read API in ANALYZE
Next
From: Alvaro Herrera
Date:
Subject: Re: not null constraints, again