9.3devel / AMD FX-8120 8-core  / centos 6.2 / Linux 2.6.32-279.11.1.el6.x86_64

Hi,

I made a test setup of 9.3devel synchronous replication (git-master as of a few 
hours ago):
two instances on 1 machine:
  master: 93_1  port 6664
  slave:  93_2  port 6665

I do nothing on either server.  I get these logs (note the ERROR-lines in the 
slave log, every 5
minutes) :

$ tail -F 
/home/aardvark/pg_stuff/pg_installations/pgsql.93_1/data/../logfile.93_1
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  received smart shutdown request
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
2012-11-09 09:42:49.717 CET 6279 LOG:  database system was shut down at 
2012-11-09 09:42:49 CET
2012-11-09 09:42:49.823 CET 6283 LOG:  autovacuum launcher started
2012-11-09 09:42:49.824 CET 6278 LOG:  database system is ready to accept 
connections
2012-11-09 09:42:53.244 CET 6329 LOG:  standby "wal_receiver_01" is now the 
synchronous standby
with priority 1

$ tail -F 
/home/aardvark/pg_stuff/pg_installations/pgsql.93_2/data/../logfile.93_2
cp: cannot stat `/home/aardvark/pg_stuff/archive_dir/000000010000000000000004': 
No such file or
directory
2012-11-09 09:42:53.144 CET 6328 LOG:  streaming replication successfully 
connected to primary
2012-11-09 09:49:01.124 CET 6323 ERROR:  lock 9 is not held
2012-11-09 09:53:02.427 CET 6323 ERROR:  lock 9 is not held
2012-11-09 09:58:03.845 CET 6323 ERROR:  lock 9 is not held
2012-11-09 10:03:05.239 CET 6323 ERROR:  lock 9 is not held
2012-11-09 10:07:51.620 CET 6323 ERROR:  lock 9 is not held
2012-11-09 10:12:53.019 CET 6323 ERROR:  lock 9 is not held
2012-11-09 10:17:54.416 CET 6323 ERROR:  lock 9 is not held
2012-11-09 10:22:55.811 CET 6323 ERROR:  lock 9 is not held


Master configuration:

data_directory = '/home/aardvark/pg_stuff/pg_installations/pgsql.93_1/data'
listen_addresses = '*'
max_connections = 100
shared_buffers = 128MB
wal_level = hot_standby
synchronous_commit = on
checkpoint_segments = 50
archive_mode = on
archive_command = 'cp %p /home/aardvark/pg_stuff/archive_dir/%f < /dev/null'
max_wal_senders = 3
synchronous_standby_names = '*'


Slave configuration:

data_directory = '/home/aardvark/pg_stuff/pg_installations/pgsql.93_2/data'
listen_addresses = '*'
port = 6665
max_connections = 100
shared_buffers = 128MB
wal_level = hot_standby
synchronous_commit = on
checkpoint_segments = 50
archive_mode = on
archive_command = 'cp %p /home/aardvark/pg_stuff/archive_dir/%f < /dev/null'
max_wal_senders = 3
synchronous_standby_names = ''
hot_standby = on
wal_receiver_status_interval = 59


It's just an ERROR-line in the log, and it may not be a real problem, but in 
any case I'd like to
know how it is caused

(I ought to add that I had not run these build-scripts for testing syncrep for 
a few weeks/months
so I may have missed some developments in setup/config)

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

Reply via email to