Hello,

we found a bug while testing the latest version of Hot Standby. Then
we could reproduce it on the unpatched HEAD, so we are going to ignore
it in the next few days.

During a Warm Standby session using current HEAD I obtained the
following error on the standby node:

---8<------8<------8<------8<------8<------8<------8<------8<------8<---
2009-01-16 16:24:01 GMT[30678]LOG:  restored log file 
"0000000100000001000000C2" from archive
2009-01-16 16:24:01 GMT[30678]FATAL:  could not open relation 
pg_tblspc/491086/467369/491103: No such file or directory
2009-01-16 16:24:01 GMT[30678]CONTEXT:  writing block 1 of relation 
pg_tblspc/491086/467369/491103
        xlog redo checkpoint: redo 1/C2001AB8; tli 1; xid 0/89982; oid 491520; 
multi 1; offset 0; online
2009-01-16 16:24:01 GMT[30665]LOG:  startup process (PID 30678) exited with 
exit code 1
2009-01-16 16:24:01 GMT[30665]LOG:  aborting startup due to startup process 
failure
2009-01-16 16:24:01 GMT[30677]DEBUG:  logger shutting down
---8<------8<------8<------8<------8<------8<------8<------8<------8<---

After setting up the session, I started an endless loop of "make
installcheck" on the primary node; the error happened after 40/50
minutes.

At the present I can't say exactly which test was responsible for
that, but this information should be obtainable by raising debug level
on the primary and comparing WAL segment numbers while looking at both
logfiles. Anyway, since the error was raised by bgwriter when running
with Hot Standby patch applied, is likely to be something to do with
the guts of checkpointing.

Best regards,
Dr. Gianni Ciolli - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gianni.cio...@2ndquadrant.it | www.2ndquadrant.it


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to