pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedcrash problem
4+ messages / 2 participants
[nested] [flat]
* crash problem
@ 2002-06-21 01:29 terry@greatgulfhomes.com
2002-06-21 04:34 ` Re: crash problem Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 4+ messages in thread
From: terry@greatgulfhomes.com @ 2002-06-21 01:29 UTC (permalink / raw)
To: pgsql-docs
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'
'.
I get the same error if I try to do dumpall.
I try looking at the triggers table and this is what I get:
devtest=# select * from pg_trigger;
ERROR: Relation pg_trigger does not have attribute
devtest=# \d pg_trigger
Table "pg_trigger"
Attribute | Type | Modifier
----------------+------------+----------
tgrelid | oid |
tgname | name |
tgfoid | oid |
tgtype | smallint |
tgenabled | boolean |
tgisconstraint | boolean |
tgconstrname | name |
tgconstrrelid | oid |
tginitdeferred | boolean |
tgnargs | smallint |
tgattr | int2vector |
tgargs | bytea |
Indices: pg_trigger_tgconstrname_index,
pg_trigger_tgconstrrelid_index,
pg_trigger_tgrelid_index
I ran a vacuum, and it did worked, but did not fix this corruption problem.
Nothing meaningful appears in the log, just messages about the "backend
terminated unexpectedly".
What do I do now? I was hoping to upgrade to 7.2.1 this weekend, but if I
cannot back it up again, I will loose all of todays work, which was pretty
significant, I added much tables and populated a bunch also.
Any ideas is appreciated.
Thanks
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: crash problem
2002-06-21 01:29 crash problem terry@greatgulfhomes.com
@ 2002-06-21 04:34 ` Tom Lane <tgl@sss.pgh.pa.us>
2002-06-21 11:46 ` Re: [DOCS] crash problem terry@greatgulfhomes.com
0 siblings, 1 reply; 4+ messages in thread
From: Tom Lane @ 2002-06-21 04:34 UTC (permalink / raw)
To: terry@greatgulfhomes.com; +Cc: pgsql-docs
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [DOCS] crash problem
2002-06-21 01:29 crash problem terry@greatgulfhomes.com
2002-06-21 04:34 ` Re: crash problem Tom Lane <tgl@sss.pgh.pa.us>
@ 2002-06-21 11:46 ` terry@greatgulfhomes.com
0 siblings, 0 replies; 4+ messages in thread
From: terry@greatgulfhomes.com @ 2002-06-21 11:46 UTC (permalink / raw)
To: 'Tom Lane' <tgl@sss.pgh.pa.us>; Postgres (E-mail) <pgsql-general@postgresql.org>
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
> -----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
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* FW: crash problem
@ 2002-06-21 02:42 terry@greatgulfhomes.com
0 siblings, 0 replies; 4+ messages in thread
From: terry@greatgulfhomes.com @ 2002-06-21 02:42 UTC (permalink / raw)
To: pgsql-docs
Looking even closer at the docs, it appears that my pg_triggers table should
have a column tgdeferrable BOOL, but it does not. When I try to create it I
get:
devtest=# alter table pg_trigger add column tgdeferrable BOOL;
ERROR: ALTER TABLE: relation "pg_trigger" is a system catalog
Is there some way that I can FORCE the creation or somehow get that column
back in there just so I can do a dump???
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
-----Original Message-----
From: terry@greatgulfhomes.com [mailto:terry@greatgulfhomes.com]
Sent: Thursday, June 20, 2002 9:30 PM
To: Postgres (E-mail)
Subject: crash problem
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'
'.
I get the same error if I try to do dumpall.
I try looking at the triggers table and this is what I get:
devtest=# select * from pg_trigger;
ERROR: Relation pg_trigger does not have attribute
devtest=# \d pg_trigger
Table "pg_trigger"
Attribute | Type | Modifier
----------------+------------+----------
tgrelid | oid |
tgname | name |
tgfoid | oid |
tgtype | smallint |
tgenabled | boolean |
tgisconstraint | boolean |
tgconstrname | name |
tgconstrrelid | oid |
tginitdeferred | boolean |
tgnargs | smallint |
tgattr | int2vector |
tgargs | bytea |
Indices: pg_trigger_tgconstrname_index,
pg_trigger_tgconstrrelid_index,
pg_trigger_tgrelid_index
I ran a vacuum, and it did worked, but did not fix this corruption problem.
Nothing meaningful appears in the log, just messages about the "backend
terminated unexpectedly".
What do I do now? I was hoping to upgrade to 7.2.1 this weekend, but if I
cannot back it up again, I will loose all of todays work, which was pretty
significant, I added much tables and populated a bunch also.
Any ideas is appreciated.
Thanks
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2002-06-21 11:46 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-06-21 01:29 crash problem terry@greatgulfhomes.com
2002-06-21 04:34 ` Tom Lane <tgl@sss.pgh.pa.us>
2002-06-21 11:46 ` terry@greatgulfhomes.com
2002-06-21 02:42 FW: crash problem terry@greatgulfhomes.com
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox