Re: [HACKERS] 7.0.2 -> 7.0.3 problem - anyone?

[ Charset ISO-8859-1 unsupported, converting... ]

I think I might have explained this wrong..

Ok, both databases had a BLCKSZ of 32k before the upgrade (in 7.0.2), one
database that I upgraded first to 7.0.3 went flawlessly, it started, I can
do every operation fine and it's BLCKSZ is 32k (so the BLCKSZ never changed
between the installs, it is exactly as it was before).. I used the exact
same procedure for my production database and it doesn't start..

If I have to dump and reload in this situation, that's fine.. You absolutely
know more than I do about PostgreSQL but I know what I did on the
development machine and it didn't have these problems -- that's why I didn't
think any dump and/or reload was needed...

When I went back to 7.0.2, I shouldn't have had to dump and restore, should
I? I never did an initdb on the 7.0.3 installation so the data (and
virtually everything else as far as data is concerned was the same as when I
was running 7.0.2

Knowing all the above, do you still think a dump and reload was required? If
so that's fine, I just need to know..

You are correct. It does not need a dump/restore.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

I think I might have explained this wrong..

Ok, both databases had a BLCKSZ of 32k before the upgrade (in 7.0.2), one
database that I upgraded first to 7.0.3 went flawlessly, it started, I can
do every operation fine and it's BLCKSZ is 32k (so the BLCKSZ never changed
between the installs, it is exactly as it was before).. I used the exact
same procedure for my production database and it doesn't start..

If I have to dump and reload in this situation, that's fine.. You absolutely
know more than I do about PostgreSQL but I know what I did on the
development machine and it didn't have these problems -- that's why I didn't
think any dump and/or reload was needed...

When I went back to 7.0.2, I shouldn't have had to dump and restore, should
I? I never did an initdb on the 7.0.3 installation so the data (and
virtually everything else as far as data is concerned was the same as when I
was running 7.0.2

Knowing all the above, do you still think a dump and reload was required? If
so that's fine, I just need to know..

-Mitch

----- Original Message -----
From: "Bruce Momjian" <pgman@candle.pha.pa.us>
To: "Mitch Vincent" <mitch@venux.net>
Cc: <pgsql-hackers@postgresql.org>; <pgsql-general@postgresql.org>
Sent: Sunday, November 12, 2000 6:34 PM
Subject: Re: [HACKERS] 7.0.2 -> 7.0.3 problem - anyone?

Block size can not be changes without dump/reload. If you think it
worked once, you are wrong. Sorry. The page headers have to be written
at the start of every block.

[ Charset ISO-8859-1 unsupported, converting... ]

I realize it's Sunday night and not many people will be checking their
email, however I must ask one final time before I take some drastic

measures

(erasing the data directory and initdb 'ing, then restoring the data

from

last night's backup, losing an entire day's worth of data) -- does

anyone

have any ideas on how I might be able to fix the problems outlined

below?

I'm nearly positive that I shouldn't have had to dump/restore or initdb
again, since I made the same changes on another machine with the same
databases, data and BLCKSZ (an upgrade to 7.0.3 without an initdb or
anything), which went flawlessly.

Thanks to anyone who could even offer a guess, I've guessed all I can

and

none of my guesses have paid off.. BTW, one might be lead to believe

that

this is a permission problem, it's not, I'm positive of that. The same

user

was accessing the same file seconds before I upgraded, that and the fact
that I changed permissions to 777 all the way down the tree to make

sure..

-Mitch

You have to dump/initdb/reload if you change the block size. Simply
recompiling is not going to work.

Cheers...

MikeA

-----Original Message-----
From: Mitch Vincent
To: pgsql-hackers@postgresql.org
Sent: 11-13-00 12:57 AM
Subject: [HACKERS] 7.0.2 -> 7.0.3 problem

I just upgraded to 7.0.3 and tried to start the backend like

/usr/local/pgsql/bin/postmaster -B 256 -o '-S 10240 -s' -D
/usr/local/pgsql/data -i > /usr/local/pgsql/postgres.log 2>&1 &

.. as I've done with 7.0.2, it failed to start and got this in my
postgresql.log :

DEBUG: Data Base System is starting up at Sun Nov 12 18:20:04 2000
FATAL 2: Read("/usr/local/pgsql/data/pg_control") failed: 2
FATAL 2: Read("/usr/local/pgsql/data/pg_control") failed: 2
Startup failed - abort

The only compilation change I made was to increase BLCKSZ to 32k

(which