You also can query the pg_replication_slots view for examining the current status of your replication slots, latest confirmed LSN, and more. pg_drop_replication_slot(): deletes a replication slot.pg_replication_slot_advance(): advances a replication slot. ![]() pg_logical_slot_peek_changes(): allows to take a look at changes from a slot without advancing it.pg_logical_slot_get_binary_changes(): retrieves binary messages from a slot. ![]() There are a few other useful functions dealing with logical decoding messages and replication slots, including the following: Note that this message doesn’t appear in any Postgres table or view as would be the case when adding data using the INSERT statement this message is solely present in the database's transaction log. When you retrieve changes from the slot again after having emitted a message, you now should see three change events: a BEGIN and a COMMIT event for the implicitly created transaction when emitting the event, and the “Hello World!” message itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |