- Notifications
You must be signed in to change notification settings - Fork4.9k
Commit0f404c5
committed
Fix assertion failure in snapshot building
Clear any potential stale next_phase_at value from the snapshotbuilder which otherwise may trip an assertion check ensuringthat there is no next_phase_at value.This can be reproduced by running 80 concurrent sessions likethe below where $c is a loop counter (assumes there has been1..$c databases created) : echo " CREATE TABLE replication_example(id SERIAL PRIMARY KEY, somedata int, text varchar(120)); SELECT 'init' FROM pg_create_logical_replication_slot('regression_slot_$c', 'test_decoding'); SELECT data FROM pg_logical_slot_get_changes('regression_slot_$c', NULL, NULL, 'include-xids', '0', 'skip-empty-xacts', '1'); " | psql -d regress_$c >>psql.log &This was originally committed as48efb23 and backpatched down tov16, but since then there have been reports of this happening onv14 and v15 as well so this is a backpatch of48efb23 down to 14.Bug: #17695Author: Masahiko Sawada <sawada.mshk@gmail.com>Reviewed-by: Alexander Lakhin <exclusion@gmail.com>Reported-by: bowenshi <zxwsbg@qq.com>Reported-by: Alexander Pyhalov <a.pyhalov@postgrespro.ru>Reported-by: Teja MuppartiDiscussion:https://postgr.es/m/17695-6be9277c9295985f@postgresql.orgBackpatch-through: v141 parenta144cf1 commit0f404c5
1 file changed
+5
-1
lines changedLines changed: 5 additions & 1 deletion
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
2028 | 2028 |
| |
2029 | 2029 |
| |
2030 | 2030 |
| |
2031 |
| - | |
| 2031 | + | |
| 2032 | + | |
| 2033 | + | |
| 2034 | + | |
2032 | 2035 |
| |
| 2036 | + | |
2033 | 2037 |
| |
2034 | 2038 |
| |
2035 | 2039 |
| |
|
0 commit comments
Comments
(0)