From: | "Christian Meunier" <jelan(at)magelo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: URGENT: pg_dump & Postgres 7.2b4 |
Date: | 2002-01-10 15:40:24 |
Message-ID: | a1kci8$2m9j$1@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
this error also appears during normal operations (querying/updating
database).
Is there a way to clean up those commit log ?, i tried to remove 0002 but it
didnt help( it was then doing error on 0002 too)
"Christian Meunier" <jelan(at)magelo(dot)com> wrote in message
news:a1kc2b$2m6h$1(at)news(dot)tht(dot)net(dot)(dot)(dot)
> Hi all, when i try to do a simple pg_dump i got the following errors:
>
> 2002-01-10 14:57:11 FATAL 2: open of /usr/local/pgsql/data/pg_clog/0000
> failed: No such file or directory
> 2002-01-10 14:57:11 DEBUG: server process (pid 1201) exited with exit
code
> 2
> 2002-01-10 14:57:11 DEBUG: terminating any other active server processes
> 2002-01-10 14:57:11 NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
> 2002-01-10 14:57:11 NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
> 2002-01-10 14:57:11 NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
> 2002-01-10 14:57:11 NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
> 2002-01-10 14:57:11 DEBUG: all server processes terminated;
reinitializing
> shared memory and semaphores
> 2002-01-10 14:57:11 DEBUG: database system was interrupted at 2002-01-10
> 14:55:48 GMT
> 2002-01-10 14:57:11 DEBUG: checkpoint record is at 0/1AD7A188
> 2002-01-10 14:57:11 DEBUG: redo record is at 0/1AD75E88; undo record is
at
> 0/0; shutdown FALSE
> 2002-01-10 14:57:11 DEBUG: next transaction id: 2550628; next oid: 294388
> 2002-01-10 14:57:11 DEBUG: database system was not properly shut down;
> automatic recovery in progress
> 2002-01-10 14:57:11 DEBUG: redo starts at 0/1AD75E88
> 2002-01-10 14:57:11 DEBUG: ReadRecord: record with zero length at
> 0/1ADD14A8
> 2002-01-10 14:57:11 DEBUG: redo done at 0/1ADD1484
> 2002-01-10 14:57:12 FATAL 1: The database system is starting up
> 2002-01-10 14:57:12 FATAL 1: The database system is starting up
> 2002-01-10 14:57:13 FATAL 1: The database system is starting up
> 2002-01-10 14:57:13 FATAL 1: The database system is starting up
> 2002-01-10 14:57:13 FATAL 1: The database system is starting up
> 2002-01-10 14:57:13 FATAL 1: The database system is starting up
> 2002-01-10 14:57:13 FATAL 1: The database system is starting up
> 2002-01-10 14:57:13 DEBUG: database system is ready
> 2002-01-10 14:57:14 ERROR: Cannot insert a duplicate key into unique
index
> eq_profile_pkey
> 2002-01-10 14:57:36 ERROR: Cannot insert a duplicate key into unique
index
> eq_profile_pkey
> 2002-01-10 14:57:57 ERROR: Cannot insert a duplicate key into unique
index
> account_pkey
> 2002-01-10 14:58:18 ERROR: Cannot insert a duplicate key into unique
index
> eq_profile_pkey
> 2002-01-10 14:58:44 ERROR: Cannot insert a duplicate key into unique
index
> eq_profile_pkey
>
> And in the console i got:
>
> pg_dump: query to get data of sequence "account_num_seq" failed: FATAL 2:
> open of /usr/local/pgsql/data/pg_clog/0000 failed: No such file or
directory
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
>
> The only file i got in directory pg_clog is : 0002
>
> Help plz.
> Thx in advance.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-01-10 15:41:50 | Re: caching subtotals: update vs sum -- aaugh! |
Previous Message | Christian Meunier | 2002-01-10 15:31:54 | URGENT: pg_dump & Postgres 7.2b4 |