diff options
| author | Amit Kapila <akapila@postgresql.org> | 2024-01-04 08:21:51 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2024-01-04 08:26:25 +0530 |
| commit | 007693f2a3ac2ac19affcb03ad43cdb36ccff5b5 (patch) | |
| tree | 548cee95ca1d16e7b7f87baa951e779bf8f0dfd1 /src/backend/utils/adt/arrayfuncs.c | |
| parent | 29275b1d177096597675b5c6e7e7c9db2df8f4df (diff) | |
| download | postgresql-007693f2a3ac2ac19affcb03ad43cdb36ccff5b5.tar.gz postgresql-007693f2a3ac2ac19affcb03ad43cdb36ccff5b5.zip | |
Track conflict_reason in pg_replication_slots.
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
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions