diff options
| author | Amit Kapila <akapila@postgresql.org> | 2025-11-28 05:21:35 +0000 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2025-11-28 05:21:35 +0000 |
| commit | e68b6adad96d414fdf24e072fdb1d41fb4b8f0b7 (patch) | |
| tree | 36cbdc3befc3b490893d4daa2184aa664ca46adb /doc/src/sgml/system-views.sgml | |
| parent | 9ccc049dfe655ca9927f7c62559ec32f4d1f94dd (diff) | |
Add slotsync_skip_reason column to pg_replication_slots view.
Introduce a new column, slotsync_skip_reason, in the pg_replication_slots
view. This column records the reason why the last slot synchronization was
skipped. It is primarily relevant for logical replication slots on standby
servers where the 'synced' field is true. The value is NULL when
synchronization succeeds.
Author: Shlok Kyal <shlok.kyal.oss@gmail.com>
Reviewed-by: shveta malik <shveta.malik@gmail.com>
Reviewed-by: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Reviewed-by: Ashutosh Sharma <ashu.coek88@gmail.com>
Reviewed-by: Hou Zhijie <houzj.fnst@fujitsu.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Discussion: https://postgr.es/m/CAE9k0PkhfKrTEAsGz4DjOhEj1nQ+hbQVfvWUxNacD38ibW3a1g@mail.gmail.com
Diffstat (limited to 'doc/src/sgml/system-views.sgml')
| -rw-r--r-- | doc/src/sgml/system-views.sgml | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/doc/src/sgml/system-views.sgml b/doc/src/sgml/system-views.sgml index 0e623e7fb86..7db8f73eba2 100644 --- a/doc/src/sgml/system-views.sgml +++ b/doc/src/sgml/system-views.sgml @@ -3102,6 +3102,49 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx </para></entry> </row> + <row> + <entry role="catalog_table_entry"><para role="column_definition"> + <structfield>slotsync_skip_reason</structfield><type>text</type> + </para> + <para> + The reason for the last slot synchronization skip. Slot + synchronization occurs only on standby servers and thus this column has + no meaning on the primary server. It is relevant mainly for logical slots + on standby servers whose <structfield>synced</structfield> field is + <literal>true</literal>. It is <literal>NULL</literal> if slot + synchronization is successful. + Possible values are: + <itemizedlist spacing="compact"> + <listitem> + <para> + <literal>wal_or_rows_removed</literal> means that the required WALs or + catalog rows have already been removed or are at the risk of removal + from the standby. + </para> + </listitem> + <listitem> + <para> + <literal>wal_not_flushed</literal> means that the standby had not + flushed the WAL corresponding to the position reserved on the failover + slot. + </para> + </listitem> + <listitem> + <para> + <literal>no_consistent_snapshot</literal> means that the standby could + not build a consistent snapshot to decode WALs from + <structfield>restart_lsn</structfield>. + </para> + </listitem> + <listitem> + <para> + <literal>slot_invalidated</literal> means that the synced slot is + invalidated. + </para> + </listitem> + </itemizedlist> + </para></entry> + </row> </tbody> </tgroup> </table> |