RE: 7.0.2 -> 7.0.3 problem
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
has
been running in a production 7.0.2 environment for quite some time).
So what's up? Just to make sure I made the permissions 777 all the way
down
to pg_control but it had no effect.
----
Hmm, I just re-installed 7.0.2 and I get the same error with it -- not
good.
My development server, which is virtually the same, did fine when I
installed 7.0.3 so I'm guessing it's not a problem across the board..
I also notice in the log that it's
Read("/usr/local/pgsql/data/pg_control")
that's failing and when I move pg_control out of the way, it's Open()
that
fails..
I did nothing but stop the postmaster, compile and install 7.0.3 and
start
the postmaster. then compiled and installed 7.0.2 again and all of the
sudden the 7.0.2 or 7.0.3 backend doesn't start -- it makes no sense.
As always, any help is appreciated. Thanks!
-Mitch
By the way, what is pg_control and what does it do?
-Mitch
----- Original Message -----
From: "Michael Ansley" <Michael.Ansley@intec-telecom-systems.com>
To: "'Mitch Vincent '" <mitch@venux.net>
Cc: <pgsql-hackers@postgresql.org>
Sent: Sunday, November 12, 2000 4:02 PM
Subject: RE: [HACKERS] 7.0.2 -> 7.0.3 problem
Show quoted text
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 problemI 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 - abortThe only compilation change I made was to increase BLCKSZ to 32k (which
has
been running in a production 7.0.2 environment for quite some time).So what's up? Just to make sure I made the permissions 777 all the way
down
to pg_control but it had no effect.----
Hmm, I just re-installed 7.0.2 and I get the same error with it -- not
good.My development server, which is virtually the same, did fine when I
installed 7.0.3 so I'm guessing it's not a problem across the board..I also notice in the log that it's
Read("/usr/local/pgsql/data/pg_control")
that's failing and when I move pg_control out of the way, it's Open()
that
fails..I did nothing but stop the postmaster, compile and install 7.0.3 and
start
the postmaster. then compiled and installed 7.0.2 again and all of the
sudden the 7.0.2 or 7.0.3 backend doesn't start -- it makes no sense.As always, any help is appreciated. Thanks!
-Mitch
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
Show quoted text
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 problemI 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 - abortThe only compilation change I made was to increase BLCKSZ to 32k (which
has
been running in a production 7.0.2 environment for quite some time).So what's up? Just to make sure I made the permissions 777 all the way
down
to pg_control but it had no effect.----
Hmm, I just re-installed 7.0.2 and I get the same error with it -- not
good.My development server, which is virtually the same, did fine when I
installed 7.0.3 so I'm guessing it's not a problem across the board..I also notice in the log that it's
Read("/usr/local/pgsql/data/pg_control")
that's failing and when I move pg_control out of the way, it's Open()
that
fails..I did nothing but stop the postmaster, compile and install 7.0.3 and
start
the postmaster. then compiled and installed 7.0.2 again and all of the
sudden the 7.0.2 or 7.0.3 backend doesn't start -- it makes no sense.As always, any help is appreciated. Thanks!
-Mitch