mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-04 08:27:19 +02:00
2bef06d516
The logical decoding machinery already preserved all the required catalog tuples, which is sufficient in the course of normal logical decoding, but did not guarantee that non-catalog tuples were preserved during computation of the initial snapshot when creating a slot over the replication protocol. This could cause a corrupted initial snapshot being exported. The time window for issues is usually not terribly large, but on a busy server it's perfectly possible to it hit it. Ongoing decoding is not affected by this bug. To avoid increased overhead for the SQL API, only retain additional tuples when a logical slot is being created over the replication protocol. To do so this commit changes the signature of CreateInitDecodingContext(), but it seems unlikely that it's being used in an extension, so that's probably ok. In a drive-by fix, fix handling of ReplicationSlotsComputeRequiredXmin's already_locked argument, which should only apply to ProcArrayLock, not ReplicationSlotControlLock. Reported-By: Erik Rijkers Analyzed-By: Petr Jelinek Author: Petr Jelinek, heavily editorialized by Andres Freund Reviewed-By: Andres Freund Discussion: https://postgr.es/m/9a897b86-46e1-9915-ee4c-da02e4ff6a95@2ndquadrant.com Backport: 9.4, where logical decoding was introduced. |
||
|---|---|---|
| .. | ||
| decode.c | ||
| launcher.c | ||
| logical.c | ||
| logicalfuncs.c | ||
| Makefile | ||
| message.c | ||
| origin.c | ||
| proto.c | ||
| relation.c | ||
| reorderbuffer.c | ||
| snapbuild.c | ||
| tablesync.c | ||
| worker.c | ||