From: | "Erik Rijkers" <er(at)xs4all(dot)nl> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |
Date: | 2013-02-12 16:13:29 |
Message-ID: | 8c0ead8a799ab16528bd2f002449b785.squirrel@webmail.xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, February 12, 2013 17:01, Alvaro Herrera wrote:
> Erik Rijkers wrote:
>> On Tue, February 12, 2013 15:55, Alvaro Herrera wrote:
>> > Create libpgcommon, and move pg_malloc et al to it
>> >
>>
>> If at all possible, it would be handy (for testers) if initdb-forcing commits are flagged as
>> such.
>
> Hmm? I don't think this patch requires an initdb at all. It doesn't
> touch the database contents at all, does it?
>
> Patches that force an initdb are flagged as such by bumping
> CATALOG_VERSION_NO.
>
I got this:
The database cluster was initialized with PG_CONTROL_VERSION 934, but the server was compiled with
PG_CONTROL_VERSION 935
HINT: It looks like you need to initdb
But I immediately admit that I could well be mistaken; it may have been an older commit that
triggered this complaint of 'needing initdb' on this particular machine. My apologies.
Thanks,
Erik Rijkers
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-02-12 16:19:21 | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |
Previous Message | Alvaro Herrera | 2013-02-12 16:01:37 | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-02-12 16:19:21 | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |
Previous Message | Andres Freund | 2013-02-12 16:05:55 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |