database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-26 01:22:12 +03:00
Code Activity

Track conflict_reason in pg_replication_slots.

Browse Source 
This patch changes the existing 'conflicting' field to 'conflict_reason'
in pg_replication_slots. This new field indicates the reason for the
logical slot's conflict with recovery. It is always NULL for physical
slots, as well as for logical slots which are not invalidated. The
non-NULL values indicate that the slot is marked as invalidated. Possible
values are:

wal_removed = required WAL has been removed.
rows_removed = required rows have been removed.
wal_level_insufficient = the primary doesn't have a wal_level sufficient
to perform logical decoding.

The existing users of 'conflicting' column can get the same answer by
using 'conflict_reason' IS NOT NULL.

Author: Shveta Malik
Reviewed-by: Amit Kapila, Bertrand Drouvot, Michael Paquier
Discussion: https://postgr.es/m/ZYOE8IguqTbp-seF@paquier.xyz
This commit is contained in:
Amit Kapila
2024-01-04 08:21:51 +05:30
parent 29275b1d17
commit 007693f2a3
8 changed files with 90 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
src/backend/replication/slotfuncs.c
View File

@ -406,10 +406,24 @@ pg_get_replication_slots(PG_FUNCTION_ARGS)
nulls[i++] = true;
else
{
if (slot_contents.data.invalidated != RS_INVAL_NONE)
values[i++] = BoolGetDatum(true);
else
values[i++] = BoolGetDatum(false);
switch (slot_contents.data.invalidated)
{
case RS_INVAL_NONE:
nulls[i++] = true;
break;
case RS_INVAL_WAL_REMOVED:
values[i++] = CStringGetTextDatum("wal_removed");
break;
case RS_INVAL_HORIZON:
values[i++] = CStringGetTextDatum("rows_removed");
break;
case RS_INVAL_WAL_LEVEL:
values[i++] = CStringGetTextDatum("wal_level_insufficient");
break;
}
}
Assert(i == PG_GET_REPLICATION_SLOTS_COLS);