> From: pgsql-hackers-ow...@postgresql.org > [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Michael Paquier > On Fri, Mar 17, 2017 at 1:47 PM, Tsunakawa, Takayuki > <tsunakawa.ta...@jp.fujitsu.com> wrote: > > BTW, does the developer of each feature have to modify the catalog version > in catversion.h? It's a bit annoying to see the patch application failure > on catversion.h. > > Committers take care of this part.
I understood the committer modifies the catalog version based on the patch content, so the patch submitter doesn't have to modify it. I'm relieved. > > Isn't it enough to modify the catalog version only when > alpha/beta/RC/final versions are released? > > That's useful at least for developers to bump it even during a development > cycle as you can notice with a hard failure at startup if a data folder > you have created is compatible with the new binaries or not. Oh, you're absolutely right. Regards Takayuki Tsunakawa -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers