git.postgresql.org Git - users/kgrittn/postgres.git/commit

projects / users / kgrittn / postgres.git / commit

summary | shortlog | log | commit | commitdiff | tree
(parent: 4c468b3) | patch

author	Heikki Linnakangas <heikki.linnakangas@iki.fi>
	Thu, 10 Feb 2011 19:00:29 +0000 (21:00 +0200)
committer	Heikki Linnakangas <heikki.linnakangas@iki.fi>
	Thu, 10 Feb 2011 19:04:02 +0000 (21:04 +0200)
commit	b186523fd97ce02ffbb7e21d5385a047deeef4f6
tree	00e70beaaa8529b291f85b214ee87fc686083cea	tree
parent	4c468b37a281941afd3bf61c782b20def8c17047	commit \| diff

Send status updates back from standby server to master, indicating how far
the standby has written, flushed, and applied the WAL. At the moment, this
is for informational purposes only, the values are only shown in
pg_stat_replication system view, but in the future they will also be needed
for synchronous replication.

Extracted from Simon riggs' synchronous replication patch by Robert Haas, with
some tweaking by me.

15 files changed:

doc/src/sgml/config.sgml		diff \| blob \| blame \| history
doc/src/sgml/monitoring.sgml		diff \| blob \| blame \| history
doc/src/sgml/protocol.sgml		diff \| blob \| blame \| history
src/backend/access/transam/xlog.c		diff \| blob \| blame \| history
src/backend/catalog/system_views.sql		diff \| blob \| blame \| history
src/backend/replication/walreceiver.c		diff \| blob \| blame \| history
src/backend/replication/walsender.c		diff \| blob \| blame \| history
src/backend/utils/misc/guc.c		diff \| blob \| blame \| history
src/backend/utils/misc/postgresql.conf.sample		diff \| blob \| blame \| history
src/include/access/xlog.h		diff \| blob \| blame \| history
src/include/catalog/pg_proc.h		diff \| blob \| blame \| history
src/include/replication/walprotocol.h		diff \| blob \| blame \| history
src/include/replication/walreceiver.h		diff \| blob \| blame \| history
src/include/replication/walsender.h		diff \| blob \| blame \| history
src/test/regress/expected/rules.out		diff \| blob \| blame \| history

Kevin Grittner's development, especially fully serializable transactions (See http://wiki.postgresql.org/wiki/Serializable for more info)