Re: Testing WAL replay by comparing before and after images again
| От | Simon Riggs |
|---|---|
| Тема | Re: Testing WAL replay by comparing before and after images again |
| Дата | |
| Msg-id | CANP8+jJzzB=UJS=pAYAM18rSzfJ+_EZS6OFq_L3T-N+aEFJVsQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Testing WAL replay by comparing before and after images again (Heikki Linnakangas <hlinnaka@iki.fi>) |
| Ответы |
Re: Testing WAL replay by comparing before and after images
again
|
| Список | pgsql-hackers |
On 4 September 2015 at 13:45, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
--
Another issue was with the new speculative insertions. Replaying a speculative insertion record sets the tuple's CTID to point to itself, like in a regular insertion. But in the original system, the CTID is set to a special speculative insertion token. The tool flagged up that difference.
I propose the attached patch (mark-speculative-insertions-in-replay.patch) to fix that in the replay routine. This is not required for correctness, but helps this tool, and seems like a good idea for debugging purposes anyway.
ISTM that the WAL record should include the speculative insertion token, so that replay can set it correctly.
That way we can always re-check that the later update matches the speculative insertion token we expect, in all cases.
In any case, the assumption that we are replaying all changes in single threaded mode is not appropriate for use with logical replication.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: