Re: Always bump PG_CONTROL_VERSION?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <jan(at)wi3ck(dot)info>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Always bump PG_CONTROL_VERSION?
Date: 2021-05-13 23:23:38
Message-ID: 1727596.1620948218@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jan Wieck <jan(at)wi3ck(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-05-13 23:25:17 Re: pgsql: autovacuum: handle analyze for partitioned tables
Previous Message Bruce Momjian 2021-05-13 23:22:58 Re: compute_query_id and pg_stat_statements