- Notifications
You must be signed in to change notification settings - Fork5
Commit2d7e591
committed
Properly re-initialize replication slot shared memory upon creation.
Slot creation did not clear all fields upon creation. After start thememory is zeroed, but when a physical replication slot was created inthe shared memory of a previously existing logical slot, catalog_xminwould not be cleared. That in turn would prevent vacuum from doing itsduties.To fix initialize all the fields. To make similar future bugs lesslikely, zero all of ReplicationSlotPersistentData, and re-order therest of the initialization to be in struct member order.Analysis: Andrew GierthReported-By: md@chewy.comAuthor: Michael PaquierDiscussion: <20160705173502.1398.70934@wrigleys.postgresql.org>Backpatch: 9.4, where replication slots were introduced1 parent6657acc commit2d7e591
1 file changed
+14
-4
lines changedLines changed: 14 additions & 4 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
272 | 272 |
| |
273 | 273 |
| |
274 | 274 |
| |
275 |
| - | |
276 |
| - | |
277 |
| - | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
278 | 278 |
| |
279 | 279 |
| |
280 |
| - | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
| 288 | + | |
| 289 | + | |
| 290 | + | |
281 | 291 |
| |
282 | 292 |
| |
283 | 293 |
| |
|
0 commit comments
Comments
(0)