Re: pgsql: Create libpgcommon, and move pg_malloc et al to it - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Create libpgcommon, and move pg_malloc et al to it
Date
Msg-id 25323.1360693641@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Create libpgcommon, and move pg_malloc et al to it  ("Erik Rijkers" <er@xs4all.nl>)
List pgsql-committers
"Erik Rijkers" <er@xs4all.nl> writes:
> On Tue, February 12, 2013 17:19, Alvaro Herrera wrote:
>> I'm not sure are you suggesting, though.  Are you saying that the commit
>> message should explicitely state "this patch requires initdb" or some
>> such?

> I was under the impression that this was habitually done in commit messages, but looking back
> through the commitlog messages it's not all that clear although sometimes catversion bumps are
> explicitly mentioned.

I think usually if the topic is mentioned in a commit message, it's to
explain why we are (or are not) forcing an initdb.  By and large, if a
patch touches catversion.h, that ought to be sufficient warning ...

            regards, tom lane


pgsql-committers by date:

Previous
From: "Erik Rijkers"
Date:
Subject: Re: pgsql: Create libpgcommon, and move pg_malloc et al to it
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Update visibility map in the second phase of vacuum.