Re: IPC/MultixactCreation on the Standby server
Dmitry <dsy.075@yandex.ru>
From: Dmitry <dsy.075@yandex.ru>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-06-27T06:41:19Z
Lists: pgsql-hackers
On 26.06.2025 19:24, Andrey Borodin wrote: > If my hypothesis is correct nextMXact will precede tmpMXact. It seems that the hypothesis has not been confirmed. Attempt #1 2025-06-26 23:47:24.821 MSK [220458] WARNING: Timed out: nextMXact 24138381 tmpMXact 24138379 2025-06-26 23:47:24.822 MSK [220540] WARNING: Timed out: nextMXact 24138382 tmpMXact 24138379 2025-06-26 23:47:24.823 MSK [220548] WARNING: Timed out: nextMXact 24138382 tmpMXact 24138379 ... pgbench (17.5) progress: 2.0 s, 0.0 tps, lat 0.000 ms stddev 0.000, 0 failed progress: 3.0 s, 0.0 tps, lat 0.000 ms stddev 0.000, 0 failed progress: 4.0 s, 482.2 tps, lat 820.293 ms stddev 1370.729, 0 failed progress: 5.0 s, 886.0 tps, lat 112.463 ms stddev 8.506, 0 failed progress: 6.0 s, 348.9 tps, lat 111.324 ms stddev 5.871, 0 failed WARNING: Timed out: nextMXact 24138381 tmpMXact 24138379 WARNING: Timed out: nextMXact 24138382 tmpMXact 24138379 WARNING: Timed out: nextMXact 24138382 tmpMXact 24138379 ... progress: 7.0 s, 0.0 tps, lat 0.000 ms stddev 0.000, 0 failed WARNING: Timed out: nextMXact 24138382 tmpMXact 24138379 Attempt #2 2025-06-27 09:18:01.312 MSK [236187] WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 2025-06-27 09:18:01.312 MSK [236225] WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 2025-06-27 09:18:01.312 MSK [236178] WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 ... pgbench (17.5) progress: 1.0 s, 830.9 tps, lat 108.556 ms stddev 10.078, 0 failed progress: 2.0 s, 839.0 tps, lat 118.358 ms stddev 19.708, 0 failed progress: 3.0 s, 623.4 tps, lat 134.186 ms stddev 15.565, 0 failed WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 WARNING: Timed out: nextMXact 24497747 tmpMXact 24497744 WARNING: Timed out: nextMXact 24497747 tmpMXact 24497744 ... progress: 4.0 s, 0.0 tps, lat 0.000 ms stddev 0.000, 0 failed WARNING: Timed out: nextMXact 24497746 tmpMXact 24497744 Best regards, Dmitry.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix test to work with non-8kB block sizes
- 7c2061bdfba7 19 (unreleased) landed
-
Fix setting next multixid's offset at offset wraparound
- 48969555447f 14.21 landed
- b9a02b9780bc 15.16 landed
- 4d689a17693e 16.12 landed
- cad40cec24f3 17.8 landed
- 02ba5e3be4f3 18.2 landed
- 4d936c3fff1a 19 (unreleased) landed
-
Add test for multixid wraparound
- 7b81be9b4267 19 (unreleased) landed
-
Set next multixid's offset when creating a new multixid
- 81416e1016dd 14.21 landed
- 8cfb174a61eb 15.16 landed
- 635166913078 16.12 landed
- 8ba61bc06386 17.8 landed
- e46041fd973c 18.2 landed
- 789d65364cde 19 (unreleased) landed
-
psql: Improve tab completion for large objects.
- 14ee8e640300 19 (unreleased) cited
-
Refactor some repetitive SLRU code
- c61678551699 19 (unreleased) cited
-
Transaction IDs wrap around, per my proposal of 13-Aug-01. More
- bc7d37a525c0 7.2.1 cited