Troubling On-line Backup LOG messages

From: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>
To: PgSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Troubling On-line Backup LOG messages
Date: 2006-03-21 16:47:35
Message-ID: 85871B49-DD01-40B4-978C-1B9FDD48A3D4@sitening.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

After a successful same-server test of the postgres on-line backup
process, I tried a test from a remote server to simulate a process
I'll need to do in a production environment soon.

After a step-by-step on-line backup, I saw the following in my logs:

2006-03-21 10:38:53 CST 1412 :LOG: archive recovery complete
2006-03-21 10:38:53 CST 1412 :LOG: could not truncate directory
"pg_multixact/offsets": apparent wraparound
2006-03-21 10:38:53 CST 1412 :LOG: could not truncate directory
"pg_multixact/members": apparent wraparound
2006-03-21 10:39:22 CST 1412 :LOG: database system is
ready2006-03-21 10:39:22 CST 1412 :LOG: transaction ID wrap limit is
2147484146, limited by database "postgres"

followed by dozens of these:

2006-03-21 10:39:22 CST 2499 :LOG: invalid server process ID -1

None of these are errors, but they don't seem like healthy messages
nonetheless. I don't see much discussion of them in the archives. Are
they cause for concern?

--
Thomas F. O'Connell
Database Architecture and Programming
Co-Founder
Sitening, LLC

http://www.sitening.com/
3004 B Poston Avenue
Nashville, TN 37203-1314
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-03-21 17:07:48 Re: PANIC: heap_update_redo: no block
Previous Message Stephan Szabo 2006-03-21 16:36:27 Re: Order of Update - Second Try