Re: [HACKERS] BLCKSZ 0?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dominic J(dot) Eidson" <sauron(at)the-infinite(dot)org>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] BLCKSZ 0?
Date: 2001-02-28 15:39:26
Message-ID: 18214.983374766@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Dominic J. Eidson" <sauron(at)the-infinite(dot)org> writes:
> DEBUG: Data Base System is starting up at Tue Feb 27 22:31:51 2001
> FATAL 2: database was initialized with BLCKSZ 0,
> but the backend was compiled with BLCKSZ 8192.
> looks like you need to initdb.

> So I tried to start up the
> DB using the (supposedly) old/original binaries, and the old data
> directory, which is when I get the above message(s).

Well, those are very clearly 7.0 or later binaries, because 6.5 didn't
have any such crosscheck. Which is probably why the field's not set,
too ... so your data directory is old but your executables aren't.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rod Taylor 2001-02-28 15:43:15 7.0 vs 7.1 running select count(*) FROM table WHERE (SELECT count(*) ) > 0;
Previous Message Dominic J. Eidson 2001-02-28 15:28:56 Re: [HACKERS] BLCKSZ 0?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaume Teixi 2001-02-28 15:44:54 Still some problems importing with COPY
Previous Message Dominic J. Eidson 2001-02-28 15:28:56 Re: [HACKERS] BLCKSZ 0?