By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,934 Members | 1,685 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,934 IT Pros & Developers. It's quick & easy.

Database Corruption ?

P: n/a
Hi all,

I am having a number of problems with a customer of ours. This customer is in Thailand so I don't have good machine direct access to their computers.

Scenario - we have a Java based POS system that we chose to run on Linux using PGSQL. This generally works quite ok, However at this particular customer they seem to be getting regular database corruptions requiring us to recreate the database on the machine. The following are the errors displayed when trying to start the database

[basspos@till1 root]$ postmaster -D /var/lib/pgsql/data

LOG: database system shutdown was interrupted at 2003-11-12 14:46:30 ICT
LOG: checkpoint record is at 1/812CFFC0
LOG: redo record is at 1/812CFFC0; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 4704776; next oid: 4616023
LOG: database system was not properly shut down; automatic recovery in progress
LOG: ReadRecord: unexpected pageaddr 1/7A2D0000 in log file 1, segment 129, offset 2949120
LOG: redo is not required
PANIC: XLogWrite: write request 1/812D0000 is past end of log 1/812D0000
LOG: startup process (pid 4672) was terminated by signal 6
LOG: aborting startup due to startup process failure

My questions are
What might cause this? I can't vouch for the users of these machines they may well be just powering them off without proper shutdown but I would hope that PGSQL is more robust than that.

Is this repairable? I am currently getting them to just drop the database and start again.

Regards

Chris Stokes
Senior Systems Consultant
Phone: +61 3 8415 9305 (Direct)
Level 5 534 Church St
Richmond Vic 3121 Aust
ch****@basssoftware.com <mailto:ch****@basssoftware.com>

BASS Software


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Chris Stokes" <Ch****@BassSoftware.com> writes:
PANIC: XLogWrite: write request 1/812D0000 is past end of log 1/812D0000


This sure looks like the symptom of the 7.3.3 failure-to-restart bug.
If you are on 7.3.3 then an update to 7.3.4 will fix it.

regards, tom lane

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

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.