You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Andres Freund 5aa2350426 Introduce replication progress tracking infrastructure. ... When implementing a replication solution ontop of logical decoding, two related problems exist: * How to safely keep track of replication progress * How to change replication behavior, based on the origin of a row; e.g. to avoid loops in bi-directional replication setups The solution to these problems, as implemented here, consist out of three parts: 1) 'replication origins', which identify nodes in a replication setup. 2) 'replication progress tracking', which remembers, for each replication origin, how far replay has progressed in a efficient and crash safe manner. 3) The ability to filter out changes performed on the behest of a replication origin during logical decoding; this allows complex replication topologies. E.g. by filtering all replayed changes out. Most of this could also be implemented in "userspace", e.g. by inserting additional rows contain origin information, but that ends up being much less efficient and more complicated. We don't want to require various replication solutions to reimplement logic for this independently. The infrastructure is intended to be generic enough to be reusable. This infrastructure also replaces the 'nodeid' infrastructure of commit timestamps. It is intended to provide all the former capabilities, except that there's only 2^16 different origins; but now they integrate with logical decoding. Additionally more functionality is accessible via SQL. Since the commit timestamp infrastructure has also been introduced in 9.5 (commit 73c986add) changing the API is not a problem. For now the number of origins for which the replication progress can be tracked simultaneously is determined by the max_replication_slots GUC. That GUC is not a perfect match to configure this, but there doesn't seem to be sufficient reason to introduce a separate new one. Bumps both catversion and wal page magic. Author: Andres Freund, with contributions from Petr Jelinek and Craig Ringer Reviewed-By: Heikki Linnakangas, Petr Jelinek, Robert Haas, Steve Singer Discussion: 20150216002155.GI15326@awork2.anarazel.de, 20140923182422.GA15776@alap3.anarazel.de, 20131114172632.GE7522@alap2.anarazel.de		11 years ago
..
Makefile	Add infrastructure for mapping relfilenodes to relation OIDs.	12 years ago
attoptcache.c	Update copyright for 2015	11 years ago
catcache.c	Use FLEXIBLE_ARRAY_MEMBER in a bunch more places.	11 years ago
evtcache.c	Update copyright for 2015	11 years ago
inval.c	Fix various typos and grammar errors in comments.	11 years ago
lsyscache.c	Add transforms feature	11 years ago
plancache.c	Fix column-privilege leak in error-message paths	11 years ago
relcache.c	Fix typo in relcache's equalPolicy()	11 years ago
relfilenodemap.c	Update copyright for 2015	11 years ago
relmapper.c	Reorganize our CRC source files again.	11 years ago
spccache.c	Update copyright for 2015	11 years ago
syscache.c	Introduce replication progress tracking infrastructure.	11 years ago
ts_cache.c	Update copyright for 2015	11 years ago
typcache.c	Apply table and domain CHECK constraints in name order.	11 years ago