HS/SR Assert server crash
От | Bruce Momjian |
---|---|
Тема | HS/SR Assert server crash |
Дата | |
Msg-id | 201005132201.o4DM19Q10877@momjian.us обсуждение исходный текст |
Ответы |
Re: HS/SR Assert server crash
Re: HS/SR Assert server crash |
Список | pgsql-hackers |
I was able to easily crash the standby server today just by starting it and connecting to it via psql. The master was idle. The failure was: LOG: streaming replication successfully connected to primaryTRAP: FailedAssertion("!(((xmax) >= ((TransactionId) 3)))",File: "procarray.c", Line: 1211)LOG: server process (PID 12761) was terminated by signal 6: Abort trapLOG: terminatingany other active server processes My master postgresql.conf was: wal_level = hot_standby # minimal, archive, or hot_standbyarchive_mode = on # allows archivingto be donearchive_command = 'cp -i %p /u/pg/archive/%f < /dev/null ' # command to use to archive a logfile segmentmax_wal_senders= 1 # max number of walsender processes My slave postgresql.conf was: port = 5433 # (change requires restart)wal_level = hot_standby # minimal, archive,or hot_standbyarchive_mode = off # allows archiving to be donearchive_command = 'cp -i %p /u/pg/archive/%f< /dev/null ' # command to use to archive a logfile segmenthot_standby = on # allowsqueries during recoverymax_wal_senders = 1 # max number of walsender processes and my slave recovery.conf was: restore_command = 'cp /u/pg/archive/%f %p' # e.g. 'cp /mnt/server/archivedir/%f %p'standby_mode = 'on'primary_conninfo= 'host=localhost port=5432' # e.g. 'host=localhost port=5432' Let me know what additional information I can supply. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com
В списке pgsql-hackers по дате отправления: