mirror of
https://github.com/outbackdingo/patroni.git
synced 2026-08-25 14:53:37 +00:00
d5d6a51e2c
Since `3.2.0` Patroni is able to create physical replication slots on replica nodes just for the case if this node at some moment will become the primary. There are two potential problems of having such slots: 1. They prevent recycling of WAL files. 2. They may affect vacuum on the primary is hot_standby_feedback is enabled. The first class of issues is already addressed by periodically calling pg_replication_slot_advance() function. However the second class of issues doesn't happen instantly, but only when the old primary switched to a replica. In this case physical replication slots that were at some moment activate will hold NOT NULL value of `xmin`, which will be propagated to the primary via hot_standby_feedback mechanism. To address the second problem we will detect that a physical replication slot is not supposed to be active, but having NOT NULL `xmin` and drop/crecreate it. Close #3146 Close #3153 Co-authored-by: Polina Bungina <[email protected]>
88 lines
5.6 KiB
Gherkin
88 lines
5.6 KiB
Gherkin
Feature: permanent slots
|
|
Scenario: check that physical permanent slots are created
|
|
Given I start postgres0
|
|
Then postgres0 is a leader after 10 seconds
|
|
And there is a non empty initialize key in DCS after 15 seconds
|
|
When I issue a PATCH request to http://127.0.0.1:8008/config with {"slots":{"test_physical":0,"postgres3":0},"postgresql":{"parameters":{"wal_level":"logical"}}}
|
|
Then I receive a response code 200
|
|
And Response on GET http://127.0.0.1:8008/config contains slots after 10 seconds
|
|
When I start postgres1
|
|
And I start postgres2
|
|
And I configure and start postgres3 with a tag replicatefrom postgres2
|
|
Then postgres0 has a physical replication slot named test_physical after 10 seconds
|
|
And postgres0 has a physical replication slot named postgres1 after 10 seconds
|
|
And postgres0 has a physical replication slot named postgres2 after 10 seconds
|
|
And postgres2 has a physical replication slot named postgres3 after 10 seconds
|
|
|
|
@slot-advance
|
|
Scenario: check that logical permanent slots are created
|
|
Given I run patronictl.py restart batman postgres0 --force
|
|
And I issue a PATCH request to http://127.0.0.1:8008/config with {"slots":{"test_logical":{"type":"logical","database":"postgres","plugin":"test_decoding"}}}
|
|
Then postgres0 has a logical replication slot named test_logical with the test_decoding plugin after 10 seconds
|
|
|
|
@slot-advance
|
|
Scenario: check that permanent slots are created on replicas
|
|
Given postgres1 has a logical replication slot named test_logical with the test_decoding plugin after 10 seconds
|
|
Then Logical slot test_logical is in sync between postgres0 and postgres1 after 10 seconds
|
|
And Logical slot test_logical is in sync between postgres0 and postgres2 after 10 seconds
|
|
And Logical slot test_logical is in sync between postgres0 and postgres3 after 10 seconds
|
|
And postgres1 has a physical replication slot named test_physical after 2 seconds
|
|
And postgres2 has a physical replication slot named test_physical after 2 seconds
|
|
And postgres3 has a physical replication slot named test_physical after 2 seconds
|
|
|
|
@slot-advance
|
|
Scenario: check permanent physical slots that match with member names
|
|
Given postgres0 has a physical replication slot named postgres3 after 2 seconds
|
|
And postgres1 has a physical replication slot named postgres0 after 2 seconds
|
|
And postgres1 has a physical replication slot named postgres2 after 2 seconds
|
|
And postgres1 has a physical replication slot named postgres3 after 2 seconds
|
|
And postgres2 has a physical replication slot named postgres0 after 2 seconds
|
|
And postgres2 has a physical replication slot named postgres3 after 2 seconds
|
|
And postgres2 has a physical replication slot named postgres1 after 2 seconds
|
|
And postgres3 has a physical replication slot named postgres0 after 2 seconds
|
|
And postgres3 has a physical replication slot named postgres1 after 2 seconds
|
|
And postgres3 has a physical replication slot named postgres2 after 2 seconds
|
|
|
|
@slot-advance
|
|
Scenario: check that permanent slots are advanced on replicas
|
|
Given I add the table replicate_me to postgres0
|
|
When I get all changes from logical slot test_logical on postgres0
|
|
And I get all changes from physical slot test_physical on postgres0
|
|
Then Logical slot test_logical is in sync between postgres0 and postgres1 after 10 seconds
|
|
And Physical slot test_physical is in sync between postgres0 and postgres1 after 10 seconds
|
|
And Logical slot test_logical is in sync between postgres0 and postgres2 after 10 seconds
|
|
And Physical slot test_physical is in sync between postgres0 and postgres2 after 10 seconds
|
|
And Logical slot test_logical is in sync between postgres0 and postgres3 after 10 seconds
|
|
And Physical slot test_physical is in sync between postgres0 and postgres3 after 10 seconds
|
|
And Physical slot postgres1 is in sync between postgres0 and postgres2 after 10 seconds
|
|
And Physical slot postgres1 is in sync between postgres0 and postgres3 after 10 seconds
|
|
And Physical slot postgres3 is in sync between postgres2 and postgres0 after 20 seconds
|
|
And Physical slot postgres3 is in sync between postgres2 and postgres1 after 10 seconds
|
|
|
|
@slot-advance
|
|
Scenario: check that permanent slots and member slots are written to the /status key
|
|
Given "status" key in DCS has test_physical in slots
|
|
And "status" key in DCS has postgres0 in slots
|
|
And "status" key in DCS has postgres1 in slots
|
|
And "status" key in DCS has postgres2 in slots
|
|
And "status" key in DCS has postgres3 in slots
|
|
|
|
@slot-advance
|
|
Scenario: check that only non-permanent member slots are written to the retain_slots in /status key
|
|
And "status" key in DCS has postgres0 in retain_slots
|
|
And "status" key in DCS has postgres1 in retain_slots
|
|
And "status" key in DCS has postgres2 in retain_slots
|
|
And "status" key in DCS does not have postgres3 in retain_slots
|
|
|
|
Scenario: check permanent physical replication slot after failover
|
|
Given I shut down postgres3
|
|
And I shut down postgres2
|
|
And I shut down postgres0
|
|
Then postgres1 has a physical replication slot named test_physical after 10 seconds
|
|
And postgres1 has a physical replication slot named postgres0 after 10 seconds
|
|
And postgres1 has a physical replication slot named postgres3 after 10 seconds
|
|
When I start postgres0
|
|
Then postgres0 role is the replica after 20 seconds
|
|
And physical replication slot named postgres1 on postgres0 has no xmin value after 10 seconds
|
|
And physical replication slot named postgres2 on postgres0 has no xmin value after 10 seconds
|