FW: [DOCS] crash problem

Started by Terry Fielderalmost 24 years ago2 messagesgeneral
Jump to latest
#1Terry Fielder
terry@greatgulfhomes.com

Well, I got standalone mode running now, and this is what I get:
bash$ postgres -D /var/lib/pgsql/data -O -P devtest
020621.08:12:37.638 [0] FATAL 1: catalog is missing 1 attribute for
relid 1219

Let me know if anyone has any ideas, else:

Looks like I'm screwed eh? Time to roll back to Wednesday nights backup I
guess.

Doh!

Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com

-----Original Message-----
From: terry@greatgulfhomes.com [mailto:terry@greatgulfhomes.com]
Sent: Friday, June 21, 2002 7:46 AM
To: 'Tom Lane'; Postgres (E-mail)
Subject: RE: [DOCS] crash problem

100% positive the dump program and database are 7.1, from the same release.
I have been intending to upgrade to 7.2, but have not actually done it on
that server yet.

I tried to run reindex, but it told me I have to use -O -P to go into
standalone mode. But it does not recognize those flags. Hmmm. So then I
went to /etc/rc.d/init.d/postgresql to put the flags directly into the
startup script, still cannot get it to start, but I notice that the version
the script says I am running is 7.0.3

I went to the site to look at the docs (about time, eh?) and made sure I got
the standalone options right, but here's what happens:
bash$ postmaster -D $PGDATA -O -P devtest
usage: postmaster [options]
-B nbufs set number of shared buffers
-D datadir set data directory
-S silent mode (disassociate from tty)
-a system use this authentication system
-b backend use a specific backend server executable
-d [1-5] set debugging level
-i listen on TCP/IP sockets as well as Unix domain
socket
-N nprocs set max number of backends (1..1024, default 32)
-n don't reinitialize shared memory after abnormal exit
-o option pass 'option' to each backend servers
-p port specify port for postmaster to listen on
-s send SIGSTOP to all backend servers if one dies
bash$

Presumably it does not like my commands, I guess there are unsupported in
7.0.3. How do I do a REINDEX in 7.0.3?

ie how do I get to standalone mode in 7.0.3?

I did not send this to the docs newsgroup, obviously I should be sending it
to the general group, I will subscribe to general and send my stuff there, I
thought I had been, sorry.

Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com

Show quoted text

-----Original Message-----
From: pgsql-docs-owner@postgresql.org
[mailto:pgsql-docs-owner@postgresql.org]On Behalf Of Tom Lane
Sent: Friday, June 21, 2002 12:35 AM
To: terry@greatgulfhomes.com
Cc: Postgres (E-mail)
Subject: Re: [DOCS] crash problem

terry@greatgulfhomes.com writes:

My database crashed earlier. It's starts up fine, and I

can use it, but I

cannot back it up, it reports this error:
bash$ pg_dump -t letter_tag_execute_types devtest >
bkletter_tag_execute_types
getTables(): SELECT (for TRIGGER) failed. Explanation from

backend: 'ERROR:

No
such attribute or function 'tgdeferrable'
'.

(1) Are you sure your pg_dump version matches your backend version?
(And exactly what version are we discussing here, anyway?)

(2) A reindex of pg_attribute might help. See the 7.2
REINDEX man page
for a reasonably complete description of how to reindex
system catalogs.
The 7.1 procedure is the same, but the docs are poorer...

regards, tom lane

PS: this is pretty far off-topic for pgsql-docs. Please
think a little
more about where to post before posting.

---------------------------(end of
broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Terry Fielder (#1)
Re: FW: [DOCS] crash problem

terry@greatgulfhomes.com writes:

Looks like I'm screwed eh? Time to roll back to Wednesday nights backup I
guess.

While you're at it, why not upgrade to something more recent than 7.0.3?

regards, tom lane