I don't know if it has anything to do with HS/SR, I haven't tried it on a 
single CVS vanilla
installation (yet).

To test with HS/SR, I've setup three 9.0devel instances (cvs as of today) on a 
single machine, one
as a primary, and two as slaves.  I used the instructions in

  http://wiki.postgresql.org/wiki/Streaming_Replication

and

./configure --prefix=/var/data1/pg_stuff/pg_installations/pgsql.sr_primary \
  --with-pgport=6565 --quiet --enable-depend --with-openssl --with-perl \
  --with-libxml --with-libxslt


These seem to work/replicate well.


Now, when restoring a 700MB dump (made with a 9.0devel pg_dump + pg_restore) 
into the primary,
errors like the following occur, on all three instances:

FATAL:  could not open file "pg_xlog/0000000100000001000000FF" (log file 1, 
segment 255): No such
file or directory

So, there are three logfiles:
  pgsql.sr_primary/logfile
  pgsql.sr_slavery/logfile
  pgsql.sr_slave02/logfile

$ grep -E 'FATAL|ERROR' pgsql.sr_*/logfile
pgsql.sr_primary/logfile:ERROR:  canceling autovacuum task
pgsql.sr_primary/logfile:ERROR:  canceling autovacuum task
pgsql.sr_primary/logfile:FATAL:  could not open file 
"pg_xlog/0000000100000001000000FF" (log file
1, segment 255): No such file or directory
pgsql.sr_primary/logfile:FATAL:  could not open file 
"pg_xlog/0000000100000001000000FF" (log file
1, segment 255): No such file or directory
pgsql.sr_primary/logfile:ERROR:  canceling autovacuum task
pgsql.sr_primary/logfile:ERROR:  canceling autovacuum task
pgsql.sr_slave02/logfile:ERROR:  could not read xlog records: FATAL:  could not 
open file
"pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such file or 
directory
pgsql.sr_slavery/logfile:ERROR:  could not read xlog records: FATAL:  could not 
open file
"pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such file or 
directory


This has happened several times, always 'segment' 255, 'log file'  1, 3 or 4.


hth,

Erik Rijkers




-- 
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