On Wed, January 27, 2010 17:38, Heikki Linnakangas wrote: > I'll commit it that way.
This is just to let you know that these commits seem to have solved the bug. I repeated the original test (700 MB pg_restore into a primary, with two replicating slaves, on one machine). Checking afterwards: $ for port in 6565 6566 6567; do psql -qtAp $port -c "select pg_database_size('${PGDATABASE}'), version()"; done 17057193792|PostgreSQL 9.0devel-sr_primary [...] 17057193792|PostgreSQL 9.0devel-sr_slavery 17057193792|PostgreSQL 9.0devel-sr_slave02 So that looked promising :) To make sure I also COPYd all tables to file and diff'ed them. There were indeed no differences. I did get at one point in the sr_slave02 log: (consecutive lines) LOG: consistent recovery state reached at 0/2000000 LOG: database system is ready to accept read only connections LOG: could not send data to client: Broken pipe LOG: unexpected EOF on client connection but apparently this is not problematic? HS/SR is a fantastic set of features. I'll keep hammering away a bit at the dynamic duo; if you have specific testing ideas, let me know. Thanks! 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