Re: Idea: cross-check versions during initdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Larry Rosenman <ler(at)lerctr(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Idea: cross-check versions during initdb
Date: 2000-10-28 16:38:53
Message-ID: 7844.972751133@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> Of course, people who manage to invoke a 6.5 or 7.0 initdb script aren't
>> going to be helped anyway by defenses we put into 7.1 initdb :-(.

> It just occured to me that people invoking pre-7.1 initdbs with new input
> files are not going to get very far because the bki files have different
> names now.

OK, but that will only protect us for the 7.0 to 7.1 transition. Future
transitions will create the risk again. I think we should try to solve
these issues now while we're thinking about them.

> a future version of genbki.sh might want to put a simple
> # PostgreSQL 7.2
> line atop its output files which initdb can check for.

Seems like a plan to me.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-10-28 16:41:19 Re: Gram.y patches for better parenthesis handling.
Previous Message Tom Lane 2000-10-28 16:35:29 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)