Re: Always bump PG_CONTROL_VERSION? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Always bump PG_CONTROL_VERSION?
Date
Msg-id 1727596.1620948218@sss.pgh.pa.us
Whole thread Raw
In response to Re: Always bump PG_CONTROL_VERSION?  (Jan Wieck <jan@wi3ck.info>)
List pgsql-hackers
Jan Wieck <jan@wi3ck.info> writes:
> On 5/13/21 6:45 PM, Tom Lane wrote:
>> Bumping the version in the commit that changes
>> things is not optional, because if you don't do that then you'll
>> probably burn some other developer also working on HEAD.  So
>> I don't want people thinking they can skip this because it was
>> done at the beginning of the development cycle.

> And we make sure this is done how?

Peer pressure?  It's not that different from N other ways to
do a patch incorrectly, of course.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: compute_query_id and pg_stat_statements
Next
From: Justin Pryzby
Date:
Subject: Re: pgsql: autovacuum: handle analyze for partitioned tables