PG version is 7.3.2 and OS is Red Hat Linux release 7.3 (Valhalla)
Thanks,
-Original Message-
From: Lee Wu
Sent: Monday, June 14, 2004 3:58 PM
To: [EMAIL PROTECTED]
Subject: table not shown
Hi all,
We have table is database which cannot be displayed by
either \d, or \dt or pg_class.
B
Hi all,
We have table is database which cannot be displayed by
either \d, or \dt or pg_class.
But we can select, DML on it.
Also relfilenode is in our base/dboid directory and timestamp does
change.
Please help!
Thanks,
---(end of broadcast)---
T
Barry Clearwater wrote:
LOG: could not open file "/var/lib/pgsql/data/pg_xlog/0001"
(log file 0, segment 1): No such file or directory
LOG: invalid primary checkpoint record
Is there any way I can recreate a checkpoint record or resurrect any
data from postgresql. How important was t
Michael;
What version of FreeBSD? What version of PostGres?
On my server, running FreeBSD 5.1 and pg 7.3, the values are
kern.ipc.shmmax: 33554432
kern.ipc.shmmin: 1
kern.ipc.shmmni: 192
kern.ipc.shmseg: 128
kern.ipc.shmall: 8192
kern.ipc.shm_use_phys: 0
shm3035K 38K 4653 16,102
Barry Clearwater <[EMAIL PROTECTED]> writes:
> How important was the 0001 file ?
Fairly :-(
You can get the database back into a startable condition with
pg_resetxlog, but it is likely that you may have lost part or
all of transactions since the last checkpoint.
Andreas Schmitz <[EMAIL PROTECTED]> writes:
>> What PG version is this?
> PostgreSQL 7.4.1 is used in this case.
Now that I look at it, your report matches Chris K-L's trouble
http://archives.postgresql.org/pgsql-hackers/2004-01/msg00530.php
which is fixed in 7.4.2.
regar
Having sucessfully crashed sql ledger and desperate to see if I can
start it again, I read a posting by Lamar Owen which helped me get a
meaningful output to debug.
Problem started when I inadvertantly started the computer at a date in
the future.
Now I found I have deleted an important file (0
Hi Tom,
PostgreSQL 7.4.1 is used in this case. I was able to fix the clog by
dd if=/dev/zero bs=8k count=1 >> Andreas Schmitz <[EMAIL PROTECTED]> writes:
> > after a harddisk filling up to a 100% the database crashed. This is
> > the output I get when I try to start the DB again. Is there any ch
