> Since you were running with fsync off, you must have had good backups or
> replication configured, because the documentation warns you that running
> with fsync=off will probably destroy your data and is only for expert users.
Yes, i know, i have a replica and slow disk.
> In case you don't hav
On 12/01/2012 9:08 PM, eshishki wrote:
14:01:59 MSK,,0,FATAL,XX002,"index ""1339592"" contains unexpected
zero page at block 328134",,"Please REINDEX it.",,,""
2012-01-12 14:02:00.042 MSK,,,5642,,4f0eaf97.160a,1,,2012-01-12
14:01:59 MSK,,0,LOG,0,"startup process (PID 5644) exited with exi
Hello,
today i restarted my postgresql 9.0 instance and it won't start.
The logs are
2012-01-12 14:01:59.976 MSK,,,5644,,4f0eaf97.160c,2,,2012-01-12
14:01:59 MSK,,0,LOG,0,"database system was not properly shut down;
automatic recovery in progress",""
2012-01-12 14:01:59.976 MSK,,,5644
On 5/24/07, Tom Lane <[EMAIL PROTECTED]> wrote:
It sounds like you have a reproducible test case --- can you make it
available to someone else?
Not very easily, Tom. The tarball files are around 35 GB (uncompressed)
and I assume they'd only work on a fairly similar system anyway.
I assume s
"Michael Nolan" <[EMAIL PROTECTED]> writes:
> Howevever, when I go to access one table, the index appears to be corrupted
> because the record I get for one query doesn't match the record key I give.
> Reindexing that table on the warm spare system fixes the problem.
> I redid setting up the warm
Sorry, I meant 8.2.4 (darn typo virus)
On 5/24/07, Michael Nolan <[EMAIL PROTECTED]> wrote:
Recently I went through the steps to refresh the database (8.3.4) on my
development server (running Fedora Core 5 Linux),
making a tarball of the live database, then restoring it on the
development serve
Recently I went through the steps to refresh the database (8.3.4) on my
development server (running Fedora Core 5 Linux),
making a tarball of the live database, then restoring it on the development
server, and running all the archived WAL files.
Everything worked fine as far as I can tell, I don'
Akash Garg <[EMAIL PROTECTED]> writes:
> Ok, I ran that command on the index files -- they are attached.
I'm a bit confused --- you mean you extracted block 41661 from each of
the index's segments? If so, only the first one is actually relevant
here.
> I notice that in file2, file2 and file3, I
Akash Garg <[EMAIL PROTECTED]> writes:
> I used oid2name to find the index files:
> 168807081
> 168807081.1
> 168807081.2
> 168807081.3
> 168807081.4
> Now how do I run the od command to find the block in question?
Rather than doing the math by hand, let dd do it:
dd bs=8k skip=41661 cou
I used oid2name to find the index files:
168807081
168807081.1
168807081.2
168807081.3
168807081.4
Now how do I run the od command to find the block in question?
Thanks,
Akash
On 6/23/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> Akash Garg <[EMAIL PROTECTED]> writes:
> > I'll try running th
Tom,
I'll try running the od command -- I'm just a little confused on where
I run it. I tried running od -x 41661 but that doesn't yield any
results. I'm assuming I have to run this command on the actual index
file itself -- how do I do this?
Thanks,
Akash
On 6/23/05, Tom Lane <[EMAIL PROTECTED
Akash Garg <[EMAIL PROTECTED]> writes:
> I'll try running the od command -- I'm just a little confused on where
> I run it. I tried running od -x 41661 but that doesn't yield any
> results. I'm assuming I have to run this command on the actual index
> file itself -- how do I do this?
See contrib
Akash Garg <[EMAIL PROTECTED]> writes:
> During a vacuum, I ran into this error:
> vacuumdb: vacuuming of database "friend" failed: ERROR: invalid page
> header in block 41661 of relation "friend_pkey"
> I've read the posts on this newsgroup and it's clear that I have to
> REINDEX to fix this. T
During a vacuum, I ran into this error:
vacuumdb: vacuuming of database "friend" failed: ERROR: invalid page
header in block 41661 of relation "friend_pkey"
I've read the posts on this newsgroup and it's clear that I have to
REINDEX to fix this. The bigger question is -- why did this happen in
t
14 matches
Mail list logo
