Re: Broken due to CVS branching? .bki has wrong info for build

From: Selena Deckelmann <selenamarie(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Broken due to CVS branching? .bki has wrong info for build
Date: 2010-07-17 19:02:12
Message-ID: AANLkTimQTcVmjnZSaTdHIbnRgVfJbHc1g4f1e18jRucF@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 17, 2010 at 10:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Selena Deckelmann <selenamarie(at)gmail(dot)com> writes:
>> I pulled the latest from the git repo, I got this error on initdb:
>
>> creating template1 database in testdb/base/1 ... initdb: input file
>> "/usr/local/pg90/share/postgresql/postgres.bki" does not belong to
>> PostgreSQL 9.0devel
>
>> The problem was having '9.1' instead of '9.0' in the first line of the .bki.
>
> Yeah, I ran into that too.  The makefiles don't have a dependency that
> forces postgres.bki to be rebuilt when you update the major version in
> configure.in.  Just delete src/backend/catalog/postgres.bki and
> rebuild/reinstall.  (Actually, as of CVS HEAD it shouldn't be a problem
> anymore because of yesterday's changes in pg_proc.h.)
>
> I'm not sure whether it's worth adding an explicit dependency to cover
> this case.  It only comes into play at major version boundaries.

Ok, that makes sense.

I rebuilt just now, and it worked fine.

Thanks!
-selena

--
http://chesnok.com/daily - me

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-07-17 19:09:06 Re: Review: Row-level Locks & SERIALIZABLE transactions, postgres vs. Oracle
Previous Message Heikki Linnakangas 2010-07-17 18:14:56 Re: Synchronous replication